| *** tvon has joined #zope3-dev | 00:09 | |
| Workblia | if anyone could look at 376 an fix it, he would save me a lot of time | 00:09 |
|---|---|---|
| Workblia | issue 376 in zope collector | 00:09 |
| Workblia | 367 | 00:09 |
| Workblia | ;) | 00:09 |
| *** bskahan has quit IRC | 00:09 | |
| *** bskahan has joined #zope3-dev | 00:10 | |
| *** tvon|x31 has joined #zope3-dev | 00:12 | |
| *** tvon has quit IRC | 00:26 | |
| *** tvon|desk has joined #zope3-dev | 00:28 | |
| *** tvon|x31 has quit IRC | 00:32 | |
| *** d2m has quit IRC | 00:32 | |
| *** bskahan has quit IRC | 00:32 | |
| *** bskahan has joined #zope3-dev | 00:33 | |
| *** tvon has joined #zope3-dev | 00:36 | |
| *** d2m has joined #zope3-dev | 00:42 | |
| *** tvon|desk has quit IRC | 00:46 | |
| *** bskahan has quit IRC | 00:52 | |
| *** tvon has quit IRC | 00:54 | |
| *** mgedmin has quit IRC | 00:58 | |
| *** bskahan has joined #zope3-dev | 01:19 | |
| _projekt01 | Workblia, you don't have committ permission on the zope3 trunk? | 01:26 |
| *** GaryPoster has quit IRC | 01:29 | |
| *** tvon|desk has joined #zope3-dev | 01:33 | |
| *** benji_york has quit IRC | 01:35 | |
| *** bskahan has quit IRC | 01:36 | |
| *** philiMAC has joined #zope3-dev | 01:42 | |
| *** philiMAC is now known as philiKON | 01:43 | |
| *** alga has quit IRC | 01:44 | |
| *** tvon has joined #zope3-dev | 01:44 | |
| *** tvon|desk has quit IRC | 01:50 | |
| *** bskahan has joined #zope3-dev | 01:51 | |
| *** mexiKON has quit IRC | 02:00 | |
| *** tvon has quit IRC | 02:06 | |
| *** tvon has joined #zope3-dev | 02:07 | |
| *** J1m has quit IRC | 02:11 | |
| *** tvon|desk has joined #zope3-dev | 02:11 | |
| *** tvon|x31 has joined #zope3-dev | 02:28 | |
| *** tvon has quit IRC | 02:28 | |
| *** GaryPoster has joined #zope3-dev | 03:34 | |
| *** GaryPoster has quit IRC | 04:05 | |
| *** GaryPoster has joined #zope3-dev | 04:08 | |
| *** vlado has quit IRC | 04:22 | |
| *** GaryPoster has quit IRC | 04:41 | |
| *** Jim7J1AJ1 has joined #zope3-dev | 04:44 | |
| *** Jim7J1AJH has quit IRC | 04:45 | |
| *** d2m has quit IRC | 04:59 | |
| *** Jim7J1AJ1 has quit IRC | 05:10 | |
| *** Jim7J1AJH has joined #zope3-dev | 05:10 | |
| *** _projekt01 has quit IRC | 05:28 | |
| *** hazmat has joined #zope3-dev | 05:41 | |
| *** beorn has joined #zope3-dev | 09:46 | |
| *** beorn has left #zope3-dev | 09:46 | |
| *** zagy has quit IRC | 10:15 | |
| *** zagy has joined #zope3-dev | 11:36 | |
| *** hazmat has quit IRC | 12:01 | |
| *** d2m has joined #zope3-dev | 12:15 | |
| *** philiKON has quit IRC | 12:22 | |
| *** zagy has quit IRC | 12:37 | |
| *** Theuni has joined #zope3-dev | 12:37 | |
| *** zagy has joined #zope3-dev | 12:53 | |
| *** mgedmin has joined #zope3-dev | 15:16 | |
| *** The|uni has joined #zope3-dev | 15:21 | |
| *** Theuni has quit IRC | 15:25 | |
| *** J1m has joined #zope3-dev | 15:37 | |
| srichter | J1m: Is it now possible to compare dicts in doctests? | 15:46 |
| srichter | (I really like how the new apidoc API turns out) | 15:48 |
| J1m | I don't know what you mean. | 15:49 |
| J1m | It has always been possible to compare dicts in doctests. | 15:49 |
| J1m | Doctest doesn't place any restrictions on comparing dicts. | 15:49 |
| srichter | but if I do: | 15:49 |
| srichter | >>> {'1': ' | 15:49 |
| J1m | Are you asking whether there is a way to consistently show dicts? | 15:49 |
| srichter | >>> {'1': 'one', '2': 'two'} | 15:50 |
| srichter | I cannot expect this order back | 15:50 |
| srichter | because items are not ordered | 15:50 |
| rejj | but you can be explicit about the contents you expect | 15:50 |
| srichter | yes, I guess so :-) | 15:50 |
| J1m | from doctest.doctestunit import pprint | 15:50 |
| J1m | pprint(d) | 15:50 |
| srichter | ahh, I used my own homebrewed one till now | 15:50 |
| srichter | cool | 15:50 |
| J1m | will sort the dict | 15:50 |
| srichter | that's what I need | 15:51 |
| srichter | thanks | 15:51 |
| J1m | This simply uses pprint with a widgth of 1. | 15:51 |
| J1m | pprint doesn't sort unless it wraps. :/ | 15:51 |
| rejj | pprint has some oddness though | 15:51 |
| srichter | yeah, I remember this discussion | 15:51 |
| J1m | rejj, how so> | 15:52 |
| J1m | rejj, how so? | 15:52 |
| rejj | the tests that fail under python 2.4 are because layers in a skin come out ordered differently than under 2.3 | 15:52 |
| rejj | and the test is using pprint | 15:52 |
| J1m | I didn't know we still has tests failing in 2.4. | 15:53 |
| J1m | I didn't know we still had tests failing in 2.4. | 15:53 |
| rejj | there's a patch in the collector (somewhere, I can't remember the number) to define __lt__ and explicitly call .sort() to resolve this | 15:53 |
| J1m | :( | 15:53 |
| rejj | but the author stated that they weren't sure this was the optimal solution | 15:53 |
| rejj | Two tests fail under 2.4 | 15:53 |
| srichter | but this was not because of that | 15:53 |
| J1m | srichter, you haven't fixed those yet? | 15:53 |
| srichter | and these two failures were fixed recently | 15:53 |
| J1m | whew | 15:53 |
| srichter | not by my but by the guy who reported them | 15:54 |
| rejj | how recent? they failed when I checked .. a few days-ish ago | 15:54 |
| srichter | recently; I dunno when | 15:55 |
| rejj | I guess I should update | 15:55 |
| srichter | J1m: can I also allow globally to ignore whitespace? | 16:00 |
| J1m | huh? | 16:01 |
| J1m | What do you mean globally? | 16:01 |
| srichter | right nwo I always say: #doctest:+NORMALIZE_WHITESPACE | 16:02 |
| J1m | You can pass flags to DocFileSuite | 16:02 |
| srichter | But I would like this flag on for the entire TXT file | 16:02 |
| srichter | oh, cool | 16:02 |
| J1m | http://docs.python.org/lib/doctest-unittest-api.html | 16:03 |
| srichter | thanks | 16:04 |
| rejj | There seems to be both a "readme.txt" and a "README.TXT" in src/zope/security/ | 16:05 |
| srichter | you are on windows | 16:06 |
| rejj | which does not work under windows | 16:06 |
| srichter | delete them both and update | 16:06 |
| rejj | svn update complains | 16:06 |
| srichter | there is only one | 16:06 |
| srichter | it's just Windows that sucks | 16:06 |
| rejj | it restores readme.txt, and then fails on README | 16:06 |
| srichter | no way, readme.txt is gone | 16:06 |
| rejj | it's restoring it. | 16:06 |
| srichter | well, then the Windows SVN client sucks | 16:07 |
| srichter | delete the entire security dir | 16:07 |
| rejj | that worked | 16:09 |
| rejj | I guess README.TXT must have been added while readme.txt still existed | 16:10 |
| rejj | heh, my first collector submission. | 16:39 |
| rejj | probably wasn't even worthy of using collector, but I'm not sure what other methods exist | 16:39 |
| srichter | rejj: don't you have checkin rights? | 16:45 |
| srichter | You should get them :-) | 16:45 |
| rejj | Not unless anon can checkin (which I'm sure is not possible) | 16:46 |
| srichter | right | 16:46 |
| srichter | so why don't you get them, if you plan to hang around for a while? | 16:46 |
| rejj | Hmmm... I guess I'm still evaluating. :) | 16:47 |
| rejj | When I find myself doing something more substantial than fixing spelling errors, I'll apply for rights | 16:47 |
| srichter | ok | 16:49 |
| srichter | spelling fixes are also very important | 16:49 |
| *** The|uni is now known as theuni | 17:02 | |
| rejj | are there any issues in the collector that would be appropriate for someone attempting to learn/get started? | 17:31 |
| *** mgedmin has quit IRC | 17:31 | |
| *** mgedmin has joined #zope3-dev | 17:32 | |
| rejj | It's hard for me to judge what's involved for most of them presently. | 17:32 |
| *** J1m has quit IRC | 18:01 | |
| *** theuni has quit IRC | 18:06 | |
| *** tarek_pala has joined #zope3-dev | 18:32 | |
| *** hazmat has joined #zope3-dev | 18:32 | |
| tarek_pala | was lower case notation for modules that contains a class was introduced by Zope 3 or it's more likelyto be a change in python code style ? | 18:34 |
| mgedmin | tarek_pala, PEP 8 recommends lower case names for modules | 18:50 |
| mgedmin | some older modules in the Python standard library do not follow that convention | 18:50 |
| mgedmin | but all newer ones do | 18:50 |
| tarek_pala | mgedmin: ok thx | 18:52 |
| tarek_pala | in pep 8 guido make a difference between two cases : | 18:52 |
| tarek_pala | library-style modules, that are lower case | 18:53 |
| tarek_pala | and class module, that has the same name as the class | 18:53 |
| tarek_pala | in caps | 18:53 |
| tarek_pala | in zope 2 those "class modules " are CapsWords | 18:54 |
| tarek_pala | not in Z3 | 18:55 |
| tarek_pala | so i was wondering if this was specific to zope 3 | 18:55 |
| mgedmin | ah, it's been a while since I last read PEP-8 | 18:55 |
| mgedmin | there was a great namegeddon in zope 3 | 18:56 |
| tarek_pala | well, that's how i understood it, since i'm french, i'm not sure at all | 18:56 |
| mgedmin | people decided that there were too many modules and they were nested too deeply | 18:56 |
| mgedmin | code was full of imports like from foo.bar.baz.SomeName.SomeName import SomeName | 18:56 |
| mgedmin | so zope 3 sources were restructured to use a flatter module hierarchy | 18:56 |
| mgedmin | and dropped the 'one class in one module' rule | 18:57 |
| mgedmin | so you could say there are no more "class modules" in zope 3 | 18:57 |
| mgedmin | and if you find a module that contains only one class, it's just a coincidence | 18:57 |
| mgedmin | there simply weren't any other classes/functions that needed to go together | 18:57 |
| mgedmin | HTH | 18:57 |
| tarek_pala | ok, very interesting | 18:57 |
| tarek_pala | thx for this explanatuon mgedmin | 18:58 |
| rejj | What's the rule deciding when the classes should be grouped into the same module? | 18:58 |
| tarek_pala | imho, i split thing when module gets too big | 19:00 |
| tarek_pala | but this is a bad rule i guess :) | 19:00 |
| mgedmin | that's the same one I use ;) | 19:01 |
| mgedmin | unless classes are clearly unrelated | 19:01 |
| rejj | I would tend to do it based on how tightly coupled the classes are | 19:01 |
| rejj | but I was just wondering if anything had been formalised for z3 dev somewhere | 19:02 |
| rejj | I don't really like the one-class-in-one-module rule, personally. If I create a (for example) custom container class, that holds custom items (and raises its own exceptions), I'd put the container class, item class, and exceptions in the same module. (assuming it made no sense to define one of those items outside the context of that container) | 19:03 |
| tarek_pala | i think the efficiency of how it is organized is told by how messy are the import section | 19:05 |
| tarek_pala | zope 3 is a model on this | 19:05 |
| *** tarek_pala is now known as tarek_away | 19:06 | |
| *** hazmat has quit IRC | 19:39 | |
| *** hazmat has joined #zope3-dev | 19:49 | |
| *** hazmat has quit IRC | 20:07 | |
| *** J1m has joined #zope3-dev | 20:10 | |
| J1m | srichter, ayt? | 20:11 |
| J1m | whimper | 20:13 |
| *** srichter has quit IRC | 20:23 | |
| *** hazmat has joined #zope3-dev | 20:46 | |
| *** tarek_away has quit IRC | 20:53 | |
| *** juka has joined #zope3-dev | 20:58 | |
| *** juka has left #zope3-dev | 20:59 | |
| *** philiKON has joined #zope3-dev | 21:01 | |
| *** niemeyer has joined #zope3-dev | 21:01 | |
| *** hazmat has quit IRC | 21:04 | |
| *** J1m has quit IRC | 22:55 | |
| *** hazmat has joined #zope3-dev | 23:27 | |
| *** niemeyer has quit IRC | 23:41 | |
| *** projekt01 has joined #zope3-dev | 23:51 | |
| projekt01 | Workblia, did the fix from last night solve your problem? | 23:54 |
| *** hazmat has quit IRC | 23:59 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!