*** th1a has quit IRC | 00:00 | |
*** th1a has joined #zope3-dev | 00:02 | |
*** philiKON has quit IRC | 00:16 | |
*** tvon has joined #zope3-dev | 00:28 | |
*** admp has joined #zope3-dev | 00:33 | |
*** RaFromBRC has quit IRC | 00:46 | |
*** RaFromBRC has joined #zope3-dev | 00:48 | |
*** hazmat has quit IRC | 01:01 | |
*** hazmat has joined #zope3-dev | 01:01 | |
*** RaFromBRC has quit IRC | 01:23 | |
*** nisha_cgx has joined #zope3-dev | 01:30 | |
*** d2m has quit IRC | 01:33 | |
*** RaFromBRC has joined #zope3-dev | 01:34 | |
*** tvon has quit IRC | 01:53 | |
*** tvon has joined #zope3-dev | 01:54 | |
*** hazmat has quit IRC | 02:16 | |
*** nisha_cgx has quit IRC | 02:16 | |
*** hazmat has joined #zope3-dev | 02:16 | |
*** nisha_cgx has joined #zope3-dev | 02:16 | |
*** RaFromBRC is now known as RaFromBRC|afk | 03:01 | |
*** projekt01 has left #zope3-dev | 03:11 | |
*** bskahan has joined #zope3-dev | 03:23 | |
*** hazmat has quit IRC | 03:24 | |
*** RaFromBRC|afk has quit IRC | 03:59 | |
*** bskahan has quit IRC | 04:03 | |
*** niemeyer has quit IRC | 04:07 | |
*** nisha_cgx has quit IRC | 04:11 | |
*** thomaskorwed has joined #zope3-dev | 04:13 | |
*** thomaskorwed has left #zope3-dev | 04:14 | |
*** BjornT has joined #zope3-dev | 04:28 | |
*** bskahan has joined #zope3-dev | 05:28 | |
*** stub has joined #zope3-dev | 05:38 | |
*** bskahan has quit IRC | 05:41 | |
*** `anthony has quit IRC | 06:33 | |
*** th1a_ has joined #zope3-dev | 07:04 | |
*** BjornT has quit IRC | 07:17 | |
*** th1a has quit IRC | 07:21 | |
*** viyyer has joined #zope3-dev | 07:38 | |
*** `anthony has joined #zope3-dev | 07:47 | |
*** bradb has quit IRC | 07:50 | |
*** bradb has joined #zope3-dev | 07:51 | |
*** Arnia has left #zope3-dev | 08:12 | |
*** hazmat has joined #zope3-dev | 09:19 | |
*** sashav has joined #zope3-dev | 10:19 | |
*** vlado has joined #zope3-dev | 10:37 | |
*** projekt01 has joined #zope3-dev | 10:45 | |
projekt01 | morning | 10:46 |
---|---|---|
*** tarek_ has joined #zope3-dev | 11:17 | |
*** `anthony has quit IRC | 11:32 | |
*** deo has quit IRC | 11:33 | |
*** efge has joined #zope3-dev | 11:41 | |
*** deo has joined #zope3-dev | 11:42 | |
*** MalcolmC has joined #zope3-dev | 12:05 | |
*** philiKON has joined #zope3-dev | 12:07 | |
*** hazmat has quit IRC | 12:11 | |
*** mgedmin has joined #zope3-dev | 12:16 | |
*** viyyer has quit IRC | 12:24 | |
*** mkerrin has joined #zope3-dev | 12:41 | |
*** d2m has joined #zope3-dev | 13:27 | |
*** J1m_ has joined #zope3-dev | 13:44 | |
*** Aiste has joined #zope3-dev | 13:47 | |
*** Arnia has joined #zope3-dev | 13:54 | |
*** lunatik has joined #zope3-dev | 14:05 | |
*** Theuni has joined #zope3-dev | 14:05 | |
*** mkerrin has quit IRC | 14:30 | |
*** d2m has quit IRC | 14:36 | |
*** viyyer has joined #zope3-dev | 14:48 | |
*** Arnia has left #zope3-dev | 15:02 | |
*** bskahan has joined #zope3-dev | 15:05 | |
*** AJC has joined #zope3-dev | 15:17 | |
AJC | is there a good Z3-based blog manager? | 15:17 |
philiKON | i don't think so | 15:17 |
* philiKON wonders why people are always asking about blog examples | 15:18 | |
AJC | heh, why not? | 15:18 |
lunatik | AJC: is there a forum ? | 15:18 |
AJC | i've done an article repository and a news page, i'm just looking for more examples | 15:18 |
lunatik | so if no forum, why a blog ? :) | 15:18 |
*** `anthony has joined #zope3-dev | 15:19 | |
AJC | lunatik, there is a simple forum in the tutorial, no? | 15:19 |
philiKON | the tutorial has the buddydemo | 15:19 |
philiKON | a very simple content object + container | 15:19 |
philiKON | if you are looking for deeper examples than that, you should read one of the two books | 15:19 |
AJC | then the book philiKON, it has a "message board" example | 15:19 |
philiKON | e.g. http://worldcookery.com | 15:19 |
J1m_ | Michael Bernstein and Andy Dustman began a weblog product at PyCon in their application sprint | 15:20 |
philiKON | yes | 15:20 |
lunatik | if you've got a forum, you've got a blog :) | 15:20 |
J1m_ | They plan to release this. | 15:20 |
philiKON | cool | 15:20 |
J1m_ | It is based on the atom standard | 15:20 |
* philiKON googles for this | 15:21 | |
* bskahan is in the process of porting a plone based blog to Z3 | 15:27 | |
lunatik | bskahan: need a hand ? :) | 15:28 |
*** J1m_ has quit IRC | 15:28 | |
bskahan | lunatik: soon, as soon soon as I'm happy with the basic weblog/entry structure I'll release that part, then I'd love a hand | 15:29 |
bskahan | at the moment its something of a learning project to help me understand skins and zcml | 15:29 |
lunatik | bskahan: I'm just coding my own blog in python | 15:30 |
lunatik | so, efforts can be join together | 15:30 |
bskahan | the code is in svn.etria.com/QuillsX3/ though it only works somedays, depending on whats going on | 15:31 |
lunatik | oki | 15:31 |
lunatik | I part on the idea that a blog is an inheritage of forum | 15:31 |
bskahan | sounds good, I'll try to spend some focused time on it this week to get it into collaborative shape | 15:31 |
lunatik | I bookmark your svn uri | 15:31 |
lunatik | can I create private query with you ? | 15:32 |
bskahan | yeah | 15:32 |
*** sarca has joined #zope3-dev | 15:43 | |
*** viyyer has quit IRC | 15:52 | |
*** BjornT has joined #zope3-dev | 16:08 | |
*** niemeyer has joined #zope3-dev | 16:15 | |
*** sashav has quit IRC | 16:32 | |
*** srichter has joined #zope3-dev | 16:41 | |
*** ChanServ sets mode: +o srichter | 16:41 | |
philiKON | srichter! | 16:44 |
*** __gotcha has joined #zope3-dev | 16:52 | |
*** mgedmin has quit IRC | 17:12 | |
*** bradb has quit IRC | 17:14 | |
*** sarca is now known as viyyer | 17:36 | |
*** Aiste has quit IRC | 17:36 | |
*** Aiste has joined #zope3-dev | 17:43 | |
*** BjornT has quit IRC | 17:46 | |
*** tvon has left #zope3-dev | 17:54 | |
*** nimfa_ has joined #zope3-dev | 17:57 | |
*** viyyer has quit IRC | 18:08 | |
*** Aiste has quit IRC | 18:10 | |
*** BjornT has joined #zope3-dev | 18:15 | |
*** deo has quit IRC | 18:17 | |
*** admp has joined #zope3-dev | 18:18 | |
*** niemeyer has quit IRC | 18:30 | |
*** nimfa_ has quit IRC | 18:32 | |
*** nimfa__ has joined #zope3-dev | 18:32 | |
*** mooded has joined #zope3-dev | 18:39 | |
*** `anthony has quit IRC | 18:50 | |
*** `anthony has joined #zope3-dev | 18:53 | |
J1m | garrett-smith, ayt? | 18:56 |
*** stub has quit IRC | 19:00 | |
*** tvon has joined #zope3-dev | 19:01 | |
*** bradb has joined #zope3-dev | 19:05 | |
*** Theuni has quit IRC | 19:10 | |
srichter | J1m: why was a IAuthentication2 interface created? | 19:11 |
srichter | can IAuthentication not be adjusted using BBB to fit the new needs? | 19:12 |
J1m | not really | 19:12 |
J1m | Interfaces are contracts | 19:12 |
J1m | There should not change | 19:12 |
J1m | They should not change | 19:13 |
srichter | mmh, but we develop interfaces all the time | 19:13 |
srichter | they change like the software changes | 19:13 |
*** mooded has quit IRC | 19:13 | |
J1m | Public interfaces should not change | 19:14 |
srichter | as long as the new interface degrades nicely to the old's behavior everything is fine | 19:14 |
srichter | mmh, maybe you are right | 19:14 |
srichter | but having version numbers behind interface names is not an ideal solution either | 19:15 |
J1m | Right, it would be better to get interfaces right the first time. :) | 19:15 |
J1m | We could add "_ex". ;) | 19:15 |
srichter | shrug | 19:16 |
srichter | so what changed on the interface so much that it needed a new version? | 19:16 |
J1m | added a logout api | 19:16 |
srichter | oh, I see, it performs logout() | 19:17 |
srichter | mmh, I think IAuthenticationLogout would have been better | 19:17 |
srichter | since the security code still depends on IAuthentication and not IAuthentication2 | 19:17 |
J1m | But that will change in 3.3 | 19:18 |
srichter | mmh, can we not add logout() to IAuthentication then | 19:19 |
srichter | ? | 19:19 |
J1m | That would change the contract. | 19:19 |
srichter | and it is part of the BBB code to detect whether logout is really provided | 19:19 |
J1m | It is? Where? | 19:19 |
srichter | no, I suggest doing this | 19:20 |
*** hazmat has joined #zope3-dev | 19:20 | |
J1m | I'd like to start doing this the right way. | 19:20 |
J1m | Once an interface is set, it shouldn't change. | 19:20 |
J1m | version numbers are a necessary evil. | 19:20 |
srichter | ok | 19:21 |
srichter | maybe eventually we will be able to cycle it around | 19:22 |
*** nimfa__ has quit IRC | 19:22 | |
srichter | i.e. in 3.3 we require IAuthentication2 and then we rename it later (in 3.6) to IAuthentication again | 19:22 |
philiKON | -1 | 19:22 |
philiKON | that will only be confusing | 19:22 |
philiKON | btw, what is this "BBB gone in 3.1" in zope.app.authentication.authentication? | 19:24 |
philiKON | same goes for ...browserplugins where ti says "# BBB, entire module gone in 3.1" | 19:25 |
J1m | It means that the backward compatibility code will go away before 3.1. | 19:25 |
philiKON | uh huh | 19:26 |
* philiKON thought we were in the process of getting 3.1 ready | 19:26 | |
J1m | yes, we are | 19:26 |
*** th1a_ is now known as th1a | 19:26 | |
philiKON | k... just wondering | 19:27 |
philiKON | svn blames garrett-smith for those lines, so i guess he'll do the cleanup when he does his refactoring | 19:28 |
J1m | He's done | 19:28 |
J1m | But he'll need to rip that stuff out before long. | 19:28 |
srichter | BBB comments are the responsibility of the community not the original author | 19:28 |
J1m | Huh? | 19:29 |
srichter | well, it is the responsibility of the community to remove all outdated BBB code before a release | 19:29 |
J1m | OK, whoever :) | 19:30 |
srichter | :-) | 19:30 |
*** lunatik has left #zope3-dev | 19:43 | |
*** insanekane has joined #zope3-dev | 19:45 | |
*** mgedmin has joined #zope3-dev | 19:53 | |
*** alga has joined #zope3-dev | 19:56 | |
*** ignas has joined #zope3-dev | 19:56 | |
insanekane | i have a funny situation with ZODB: I have a Zeo server running. I open one python shell, and i add an object to root, and then commit. i open another python shell, and read root, and it comes out ok. then, i go back to the first shell, add something else. i then switch to the second shell, and print the values in root, and the added item isnt there. however, when i restart the second shell, and print the value of root, the added items are there. Is th | 19:56 |
philiKON | insanekane, did you commit the transaction? | 19:57 |
insanekane | philiKON: yes | 19:57 |
insanekane | philiKON: the thing is, (if i didnt commit) then the value will never come no matter how many times i restart the second shell | 19:57 |
insanekane | philiKON: but it does come *if* i restart .. | 19:58 |
insanekane | philiKON: my code is about 4-5 lines, mostly copied from the examples | 19:58 |
*** niemeyer has joined #zope3-dev | 19:58 | |
philiKON | sorry, no idea | 19:59 |
*** vlado is now known as vlado|away | 19:59 | |
*** MalcolmC has quit IRC | 19:59 | |
insanekane | philiKON: isnt it supposed to transparently update the changed objects ? | 19:59 |
*** J1m is now known as J1m-away | 20:00 | |
philiKON | think so | 20:00 |
*** nimfa__ has joined #zope3-dev | 20:04 | |
efge | insanekane: you have to sync the transaction to see other modified obejcts | 20:13 |
efge | sync the connection, rather | 20:14 |
mgedmin | I have to admit that ZODB syncrhonization mystifies me | 20:14 |
*** insanekane has quit IRC | 20:14 | |
mgedmin | is there anywhere I could read about it? | 20:15 |
efge | hm no idea, appart from zodb-dev archives :) | 20:15 |
efge | all Tim's emails there are interesting | 20:15 |
* mgedmin nods | 20:15 | |
efge | in Zope 2.7 that would be self._p_jar.sync(), dunno about Zope 3 | 20:16 |
*** insanekane has joined #zope3-dev | 20:16 | |
*** hazmat has quit IRC | 20:17 | |
efge | note, syncing the connection aborts the current transactions | 20:18 |
*** tvon has quit IRC | 20:23 | |
philiKON | efge, persistency is the same in z3 | 20:25 |
philiKON | so, all persistent objects should still have _p_jar | 20:26 |
*** nisha_cgx has joined #zope3-dev | 20:26 | |
philiKON | efge, as to understanding what that means: syncing is like the 'svn up' of ZODB? | 20:26 |
mgedmin | more like svn revert -r; svn up, since syncing aborts your transaction and removes your changes | 20:27 |
*** hazmat has joined #zope3-dev | 20:28 | |
philiKON | right | 20:28 |
philiKON | :) | 20:28 |
philiKON | so, is MVCC something that deals with conflicts arising from two independent zeo instances trying to commit (while one of them shoudl really do a sync())? | 20:30 |
*** vlado|away has quit IRC | 20:30 | |
*** vlado|away has joined #zope3-dev | 20:30 | |
*** tvon has joined #zope3-dev | 20:32 | |
insanekane | philiKON: whats this sync() ? | 20:34 |
philiKON | method of your zodb connection object | 20:34 |
insanekane | philiKON: what does it do ? | 20:34 |
philiKON | zodb connection == pickle jar (_p_jar) | 20:34 |
philiKON | it syncs your current connection with what happened on the ZEO server | 20:34 |
insanekane | philiKON: does it poll for invalidations from the server ? | 20:34 |
*** tarek_ has quit IRC | 20:35 | |
insanekane | philiKON: oh ... so the app developer has the resonsibility to sync ? | 20:35 |
philiKON | in zope 3 not | 20:36 |
philiKON | but when working with plain zodb, yes | 20:36 |
insanekane | philiKON: oh wow ... no wonder | 20:36 |
philiKON | in plain zodb, you have the reponsiblity to sync and commit transactions | 20:36 |
insanekane | philiKON: no wonder my values werent being transfered properly ... | 20:36 |
philiKON | zope 3 does this automatically for you | 20:36 |
insanekane | philiKON: ok, transactions i can understand ... but shouldnt the ClientStorage automatically sync with the server ? | 20:37 |
mgedmin | zope 3 calls sync? | 20:37 |
*** Arnia has joined #zope3-dev | 20:37 | |
philiKON | mgedmin, i guess it somewhere does | 20:37 |
insanekane | philiKON: wouldnt it be inefficient for me sync rather than if ClientStorage syncs ? | 20:37 |
mgedmin | this is interesting | 20:37 |
philiKON | mgedmin, how else would it work? | 20:37 |
mgedmin | I assumed that it was enough to just call transaction.commit | 20:37 |
mgedmin | every now and then | 20:37 |
mgedmin | and everything else would Just Work | 20:37 |
philiKON | i presume that upon a zope request, something like this happens: | 20:38 |
philiKON | sync() | 20:38 |
philiKON | do_stuff() | 20:38 |
philiKON | commit() | 20:38 |
* philiKON is guessing wildly | 20:38 | |
insanekane | zodb3-3.3 fails 1 unit test | 20:39 |
insanekane | aha ... philiKON, now ZODB works ... i didnt know abt sync() ... it should be mentioned in the docs | 20:43 |
insanekane | philiKON: is sync() a very expensive call ? ie, should I keep sync()-ing in GUI Idle events ? | 20:44 |
insanekane | philiKON: and, is there any way to flush some object from the cache manually ? and also, and to always keep some object in the cache | 20:45 |
philiKON | sorry, noooooo idea | 20:46 |
philiKON | i really don't know much about zodb | 20:46 |
insanekane | philiKON: sorry if im asking stupid questions :) | 20:46 |
insanekane | philiKON: ok | 20:46 |
philiKON | those don't sound like stupid questions | 20:47 |
philiKON | by looking at the code, sync() invokes the storage's sync() | 20:47 |
mgedmin | that doesn't inspire confidence in zodb, does it? | 20:47 |
mgedmin | when zope 3 gurus claim they don't understand it... | 20:48 |
mgedmin | ;-) | 20:48 |
philiKON | mgedmin, well, truth is, i'm very confident in the zodb | 20:48 |
philiKON | because it rarely fails me even though i understand nearly nothing about it :) | 20:48 |
insanekane | philiKON: good answer :) | 20:49 |
insanekane | philiKON: any idea how to configure Zope3 with a ZEO instance ? there seems not be an example of this | 20:51 |
insanekane | philiKON: sorry, to use a zope instance .. | 20:51 |
insanekane | err | 20:51 |
insanekane | zeo instance | 20:51 |
insanekane | to configure zope3 to use a zeo intance | 20:51 |
* mgedmin needs to translate widget error messages | 21:01 | |
*** efge has left #zope3-dev | 21:12 | |
*** admp has quit IRC | 21:14 | |
*** ignas has quit IRC | 21:16 | |
*** insanekane has quit IRC | 21:17 | |
mgedmin | error rendering in zope 3 goes as follows: | 21:20 |
mgedmin | 1. widget_row macro calls widget.error() | 21:21 |
mgedmin | 2. BrowserWidget.error gets a view providing IWidgetInputErrorView and calls view.snippet() | 21:21 |
mgedmin | 3. WidgetInputErrorView.snippet calls self.context.doc(), escapes the result with cgi.escape, and puts the result into a <span> element | 21:22 |
*** admp has joined #zope3-dev | 21:22 | |
mgedmin | 4. ValidationError.doc() returns self.__clas__.__doc__ | 21:22 |
mgedmin | self.__class__.__doc__ is a MessageID | 21:22 |
mgedmin | but you have to translate those explicitly, AFAIU | 21:23 |
philiKON | wow is this complicated | 21:23 |
mgedmin | if you just do cgi.escape(_('...')), '...' won't be translated | 21:23 |
mgedmin | QED | 21:23 |
srichter | philiKON: yes, it is; I hope Gary's refactorings for 3.2 will make things much easier | 21:23 |
*** SteveA_ has joined #zope3-dev | 21:23 | |
philiKON | mgedmin, right | 21:23 |
srichter | mgedmin: good catch | 21:23 |
philiKON | mgedmin, it should be cgi.escape(translate(the_msgid)) | 21:23 |
srichter | yep\ | 21:24 |
philiKON | where translate is zope.i18n.translate | 21:24 |
philiKON | mgedmin, also _(some_variable) is bogus | 21:24 |
philiKON | mgedmin, the extractor script will never catch it | 21:24 |
philiKON | it should be: | 21:24 |
philiKON | class SomeValidatorError: | 21:24 |
philiKON | _("""doc string""") | 21:24 |
mgedmin | anyway, I have an existing web text customization/translation system, and I want to integrate widget error translations with it | 21:24 |
mgedmin | philiKON, wrong | 21:24 |
mgedmin | it should be __doc__ = _("""doc string""") | 21:24 |
mgedmin | and it is so everywhere | 21:24 |
philiKON | ok, even that | 21:24 |
philiKON | great | 21:24 |
*** alga has quit IRC | 21:25 | |
* philiKON shuts up then | 21:25 | |
mgedmin | at least I haven't noticed _(variable) anywhere yet | 21:25 |
* philiKON used to, but he got rid of them back in the x3.0 days | 21:25 | |
hazmat | philiKON, barnes and noble us just pushed delivery of your book till end of april | 21:27 |
hazmat | fwiw | 21:27 |
*** nimfa__ is now known as Aiste | 21:27 | |
*** admp has quit IRC | 21:27 | |
*** SteveA has quit IRC | 21:28 | |
*** Babalorixa has joined #zope3-dev | 21:29 | |
*** admp has joined #zope3-dev | 21:32 | |
*** admp has quit IRC | 21:36 | |
*** admp has joined #zope3-dev | 21:38 | |
*** Arnia has left #zope3-dev | 21:38 | |
mgedmin | WidgetInputError.__init__ has an optional keyword argument 'errors' | 21:40 |
mgedmin | the docstring says it is a ValidationError, or a list of ValidationError objects | 21:40 |
mgedmin | yet WidgetInputError.doc() assumes it is always a single ValidationError | 21:40 |
mgedmin | and the constructor may happily assign the default value which is None and is neither a list nor a ValidationError object | 21:41 |
*** alga has joined #zope3-dev | 21:53 | |
*** RaFromBRC has joined #zope3-dev | 21:53 | |
*** bskahan has quit IRC | 21:54 | |
*** nisha_cgx has quit IRC | 22:45 | |
mgedmin | you can't post-mortem debug failed doctests :-( | 22:50 |
*** SteveA_ has quit IRC | 22:51 | |
*** SteveA_ has joined #zope3-dev | 22:52 | |
philiKON | hazmat, thanks for the info | 23:06 |
philiKON | :( | 23:06 |
J1m-away | mgedmin, I do all the time. | 23:07 |
*** J1m-away is now known as J1m | 23:07 | |
J1m | mgedmin, this is a bug. I think garrett-smith pointed this out to me recently. | 23:08 |
mgedmin | maybe I am doing something wrong then | 23:08 |
* mgedmin is suddenly confused | 23:09 | |
J1m | I thought whoever pointed out to me was going to fix it or submit an issue. | 23:09 |
mgedmin | uh, J1m, what exactly are you talking about? | 23:09 |
J1m | mgedmin, dang, sorry | 23:09 |
* mgedmin also realizes that he was looking at an older snapshot of Zope 3 trunk when he investigated error message translation | 23:09 | |
mgedmin | dang | 23:10 |
J1m | I was responding to *both* of your comments, in reverse order. :) | 23:10 |
mgedmin | both? I made three comments :) | 23:10 |
J1m | wrt doctest post-mortem debugging: | 23:10 |
J1m | mgedmin, I do all the time. | 23:10 |
J1m | It works for me | 23:10 |
mgedmin | ./test.py -D? | 23:10 |
J1m | yes | 23:10 |
J1m | wrt widget input errors | 23:11 |
J1m | mgedmin, this is a bug. I think garrett-smith pointed this out to me recently. | 23:11 |
J1m | I thought whoever pointed out to me was going to fix it or submit an issue. | 23:11 |
J1m | Does that help? | 23:11 |
J1m | Note that (wrd doctest), you have to use zope.testing.doctest (not doctest) | 23:11 |
*** RaFromBRC is now known as RaFromBRC|lunch | 23:12 | |
J1m | also, errors in functional-test zcml processing have to be handled separately. | 23:12 |
J1m | -D only works for failed tests. Not for test-runner setup. | 23:12 |
mgedmin | re test.pt -D: operator error, it does indeed work | 23:12 |
J1m | k | 23:12 |
mgedmin | only pdb doesn't find the source file and thus cannot show the source | 23:13 |
J1m | It normally does for me. | 23:13 |
mgedmin | re error translation: it turns out I was looking at a Zope 3 snapshot from February 2005 | 23:13 |
mgedmin | it might be fixed on the trunk | 23:13 |
J1m | Perhaps you renamed a directory | 23:13 |
mgedmin | > <string>(1)?() | 23:13 |
mgedmin | (Pdb) l | 23:13 |
mgedmin | [EOF] | 23:13 |
J1m | try emoving all your pyc files. | 23:13 |
J1m | try removing all your pyc files. | 23:14 |
mgedmin | I'll try that | 23:14 |
*** tonico has joined #zope3-dev | 23:14 | |
mgedmin | the important thing is to know that it's *supposed* to work | 23:14 |
J1m | The <string> thing means it's not a pyc thing | 23:14 |
J1m | doctest tries to make showing source lines work | 23:15 |
mgedmin | hm... | 23:15 |
J1m | It does at least most of the time for me. | 23:15 |
mgedmin | ok, I'll investigate that tomorrow | 23:16 |
mgedmin | thanks for your comments! | 23:16 |
*** mgedmin has quit IRC | 23:17 | |
*** tvon has quit IRC | 23:21 | |
*** Babalorixa has quit IRC | 23:28 | |
*** Aiste has quit IRC | 23:42 | |
*** admp has quit IRC | 23:50 | |
*** admp has joined #zope3-dev | 23:51 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!