| *** torkel_ has quit IRC | 00:07 | |
| *** gumpa-afk has left #zope3-dev | 00:11 | |
| *** jinty has joined #zope3-dev | 00:28 | |
| *** projekt01_ is now known as projekt01 | 00:29 | |
| *** wrobel has quit IRC | 00:31 | |
| *** flox has quit IRC | 00:35 | |
| *** schwendinger has joined #zope3-dev | 00:42 | |
| *** RaFromBRC has joined #zope3-dev | 00:50 | |
| *** jhauser has quit IRC | 00:56 | |
| *** schwendinger has quit IRC | 01:00 | |
| SmokeyD | hi all. I see that when I use this in my zpt tal:content='python: "%s<br />%s"%(budgettype,periodname)' the <br /> is translated into <br /> | 01:05 |
|---|---|---|
| *** batlogg has quit IRC | 01:05 | |
| SmokeyD | how do I prevent this? | 01:05 |
| rocky | SmokeyD: place "structure" in front of the python: part | 01:06 |
| rocky | so it would be like: zpt tal:content='structure python: "%s<br />%s"%(budgettype,periodname)' | 01:06 |
| SmokeyD | ok thanks | 01:06 |
| rocky | np | 01:06 |
| SmokeyD | Perfect! It works. | 01:06 |
| rocky | great :) | 01:07 |
| * rocky is on a role tonight... made one person happy with a quick answer in plone 5min earlier :) | 01:07 | |
| rocky | #plone rather | 01:07 |
| *** vlado has joined #zope3-dev | 01:15 | |
| *** russf_ has joined #zope3-dev | 01:31 | |
| *** benji has quit IRC | 01:38 | |
| *** russf has quit IRC | 01:38 | |
| *** jinty has quit IRC | 01:40 | |
| *** J1m has quit IRC | 01:42 | |
| *** russf has joined #zope3-dev | 01:44 | |
| *** russf_ has quit IRC | 01:44 | |
| *** yota has quit IRC | 01:45 | |
| *** russf_ has joined #zope3-dev | 01:53 | |
| *** russf has quit IRC | 01:54 | |
| *** russf_ has quit IRC | 01:57 | |
| *** russf has joined #zope3-dev | 01:57 | |
| *** russf has quit IRC | 02:01 | |
| *** volvox has quit IRC | 02:03 | |
| *** RaFromBRC has quit IRC | 02:05 | |
| *** ktwilight has quit IRC | 02:13 | |
| *** rocky has quit IRC | 02:15 | |
| *** RaFromBRC has joined #zope3-dev | 02:17 | |
| *** rocky has joined #zope3-dev | 02:18 | |
| *** markup_ has quit IRC | 02:20 | |
| *** xenru has quit IRC | 02:29 | |
| *** xenru has joined #zope3-dev | 02:31 | |
| *** markup_ has joined #zope3-dev | 02:32 | |
| *** ktwilight has joined #zope3-dev | 02:43 | |
| *** projekt01 has quit IRC | 02:46 | |
| *** rocky is now known as rocky|Zzz | 03:00 | |
| *** vlado has quit IRC | 03:18 | |
| *** markup_ has left #zope3-dev | 03:23 | |
| *** philiKON has quit IRC | 03:29 | |
| *** benji has joined #zope3-dev | 03:44 | |
| *** Theuni has quit IRC | 04:18 | |
| *** Theuni has joined #zope3-dev | 04:22 | |
| *** niemeyer has quit IRC | 05:27 | |
| *** alecm has quit IRC | 05:40 | |
| *** MiUlEr has joined #zope3-dev | 06:40 | |
| *** alecm has joined #zope3-dev | 06:55 | |
| *** natea_ has quit IRC | 06:59 | |
| *** natea has joined #zope3-dev | 07:02 | |
| *** batlogg has joined #zope3-dev | 07:07 | |
| *** natea has quit IRC | 07:28 | |
| *** stub has joined #zope3-dev | 07:38 | |
| *** batlogg has quit IRC | 07:53 | |
| *** batlogg has joined #zope3-dev | 07:56 | |
| *** jukart has joined #zope3-dev | 07:59 | |
| *** eins has joined #zope3-dev | 08:16 | |
| *** baijum has joined #zope3-dev | 08:20 | |
| *** alecm has quit IRC | 08:32 | |
| *** MiUlEr has quit IRC | 08:41 | |
| *** dobee has joined #zope3-dev | 08:44 | |
| *** hdima has joined #zope3-dev | 09:04 | |
| *** alecm has joined #zope3-dev | 09:09 | |
| *** zagy has joined #zope3-dev | 09:11 | |
| *** dunny has quit IRC | 09:19 | |
| *** yota has joined #zope3-dev | 09:24 | |
| *** BjornT has quit IRC | 09:25 | |
| *** BjornT has joined #zope3-dev | 09:25 | |
| *** wrobel has joined #zope3-dev | 09:32 | |
| *** romanofs1i has joined #zope3-dev | 09:32 | |
| *** schwendinger has joined #zope3-dev | 09:34 | |
| romanofs1i | moin | 09:35 |
| *** MJ has joined #zope3-dev | 09:38 | |
| *** romanofski has quit IRC | 09:39 | |
| *** romanofs1i is now known as romanofski | 09:39 | |
| *** alecm has quit IRC | 09:53 | |
| *** kobold has joined #zope3-dev | 10:09 | |
| *** philiKON has joined #zope3-dev | 10:18 | |
| *** J1m has joined #zope3-dev | 10:20 | |
| *** MJ has quit IRC | 10:24 | |
| *** RaFromBRC has quit IRC | 10:26 | |
| *** flox has joined #zope3-dev | 10:33 | |
| *** ktwilight has quit IRC | 10:36 | |
| *** ktwilight has joined #zope3-dev | 10:36 | |
| *** dunny has joined #zope3-dev | 10:48 | |
| *** dsh has joined #zope3-dev | 11:06 | |
| *** ignas has joined #zope3-dev | 11:06 | |
| *** dsh is now known as dsh_ | 11:06 | |
| dsh_ | hi! | 11:07 |
| dsh_ | could someone give me an start point for using sqlalchemy with Zope3? I don't want to integration like sqlos. I just neet to use it from my classes. | 11:08 |
| philiKON | dsh_, look at z3c.zalchemy in svn.zope.org | 11:11 |
| dsh_ | hmmm, ""z3c.zalchemy" integrates the object relational mapper SQLAlchemy into Zope 3 as SQLOS integrates sqlobject." | 11:12 |
| dsh_ | philiKON, thanks | 11:13 |
| eins | dsh_ keep in mind that you won't be able to have several sites with zalchemy though | 11:15 |
| dsh_ | eins, is it impossible? why? | 11:16 |
| eins | there's no way to have several sqlalchemy engines for one class, thats why | 11:17 |
| eins | you bind one class to one engine | 11:18 |
| dsh_ | eins, I see. Actually I just need to use postgresql from my zope3's app. Could you advice me the best method for it? | 11:19 |
| eins | i can't. we are using our own o-r mapper | 11:19 |
| dsh_ | I just need to execute my sql query and get the result. | 11:20 |
| dsh_ | is it possible to use psycopg2? | 11:20 |
| kobold | dsh_: you can use pyscopgda. | 11:22 |
| eins | dsh_ I have no experience with postgresql | 11:23 |
| *** tarek has joined #zope3-dev | 11:25 | |
| *** MJ has joined #zope3-dev | 11:27 | |
| *** timte has joined #zope3-dev | 11:38 | |
| *** projekt01 has joined #zope3-dev | 11:39 | |
| *** jinty has joined #zope3-dev | 12:02 | |
| *** BjornT has quit IRC | 12:10 | |
| *** dsh_ has left #zope3-dev | 12:13 | |
| *** BjornT has joined #zope3-dev | 12:16 | |
| baijum | Which is better? 'from zope import interface' or 'from zope.interface import Interface' | 12:20 |
| baijum | when writing documentation | 12:21 |
| philiKON | whatever you prefer | 12:21 |
| baijum | philiKON: which is prefered in your book (sorry, I don't have your book) | 12:23 |
| philiKON | from zope.interface import Interface | 12:23 |
| baijum | what if the name is a builtin, eg:- from zope.security.proxy import isinstance | 12:24 |
| *** tlotze has joined #zope3-dev | 12:26 | |
| tlotze | hi | 12:26 |
| tlotze | Nowadays, what is the recommended way to find out an object's parent and name? Should one go through zapi, or access ILocation's __parent__ and __name__ directly? | 12:27 |
| *** jukart has quit IRC | 12:28 | |
| philiKON | tlotze, zope.traversing.api.getParent | 12:29 |
| tlotze | oh, something new every day ;o) | 12:29 |
| tlotze | I mean, sth new to learn... | 12:29 |
| philiKON | zapi.getParent is zope.traversing.api.getParent | 12:30 |
| philiKON | same with getName | 12:30 |
| tlotze | k, given this is the recommended way, what is evil about accessing __parent__ and __name__ directly even though they are part of an interface? | 12:30 |
| philiKON | no, i wouldn't consider that evil | 12:31 |
| *** jukart has joined #zope3-dev | 12:31 | |
| tlotze | Then what is better about using the traversing api? | 12:31 |
| philiKON | more indirection ;) | 12:31 |
| philiKON | the traversing api makes things flexible when you don't have ILocations | 12:31 |
| philiKON | but if you know already that you have an ILocation, don't bother with the traversing api | 12:32 |
| tlotze | ah, that last sentence makes it clear | 12:32 |
| *** xenru has quit IRC | 12:57 | |
| *** kobold has quit IRC | 13:00 | |
| *** dunny has quit IRC | 13:01 | |
| *** baijum has quit IRC | 13:08 | |
| *** Aiste has quit IRC | 13:20 | |
| *** tarek has quit IRC | 13:20 | |
| *** baijum has joined #zope3-dev | 13:22 | |
| *** kobold has joined #zope3-dev | 13:28 | |
| *** Aiste has joined #zope3-dev | 13:38 | |
| *** jukart has quit IRC | 13:39 | |
| *** rocky|Zzz is now known as rocky | 13:40 | |
| rocky | good morning | 13:40 |
| *** kobold has quit IRC | 13:42 | |
| *** rocky is now known as rocky|away | 14:19 | |
| *** benji has quit IRC | 14:22 | |
| *** mkerrin has joined #zope3-dev | 14:22 | |
| *** J1m has quit IRC | 14:43 | |
| *** rocky|away is now known as rocky | 14:52 | |
| * baijum renamed 'Zope 3 Distilled' to 'Zope Guide', http://kpug.zwiki.org/ZopeGuide | 15:05 | |
| philiKON | baijum, hmm. i think the name should at least contain a hint regarding the audience | 15:06 |
| baijum | you mean either 'Zope Developer Guide' or 'Zope User Guide' ? | 15:07 |
| philiKON | well, something along those lines | 15:07 |
| philiKON | why not Zope 3 Developer Guide? | 15:08 |
| baijum | i thought to add few chapter on Five, so droped 3 | 15:08 |
| philiKON | oh, that makes sense | 15:08 |
| philiKON | sure, drop the 3 | 15:08 |
| philiKON | but be explicit that it's Zope 3 centric | 15:08 |
| philiKON | baijum, so, perhaps we should combine your Zope Guide with the existing (Zope 2 based) ZopeDeveloperGuide? | 15:09 |
| philiKON | there oculd be 3 parts: | 15:10 |
| philiKON | - common Zope 3 technology usable in both platforms | 15:10 |
| philiKON | - Zope 2 specifics | 15:10 |
| philiKON | - Zope 3 specifics | 15:10 |
| baijum | yes, we will do this, first I will complete 'Zope 3 specifics' part | 15:11 |
| *** natea has joined #zope3-dev | 15:13 | |
| philiKON | baijum, ok | 15:14 |
| * baijum wonder whether this will be a competition for philiKON's book :) | 15:15 | |
| philiKON | well, writing an online guide is a lot of work | 15:16 |
| philiKON | but it's not comparable with a 600 page book | 15:16 |
| philiKON | :) | 15:16 |
| philiKON | i've spent thousands of hours on this book. i recommend you don't do the same but enjoy life :) | 15:17 |
| philiKON | that said, i think it's great to have free online docs for zope | 15:17 |
| philiKON | they won't compete | 15:17 |
| philiKON | people will read the guide and see if they like zope | 15:17 |
| philiKON | if they do, they'll buy the book | 15:17 |
| MJ | In other words, Phillipp is saying "So it better be good" ;) | 15:18 |
| philiKON | well, actually no | 15:18 |
| philiKON | the guide is built by volunteer work | 15:18 |
| * MJ is having you on. | 15:18 | |
| philiKON | you can't compare that to a professional book | 15:19 |
| *** benji has joined #zope3-dev | 15:24 | |
| *** jukart has joined #zope3-dev | 15:36 | |
| *** niemeyer has joined #zope3-dev | 15:37 | |
| *** BjornT has quit IRC | 15:38 | |
| *** BjornT has joined #zope3-dev | 15:43 | |
| *** alga has joined #zope3-dev | 15:51 | |
| *** jukart has quit IRC | 15:57 | |
| *** jukart has joined #zope3-dev | 16:03 | |
| *** jukart has quit IRC | 16:17 | |
| *** jukart has joined #zope3-dev | 16:17 | |
| *** gumpa has joined #zope3-dev | 16:27 | |
| *** alga has quit IRC | 16:33 | |
| *** kobold has joined #zope3-dev | 16:36 | |
| *** gumpa is now known as gumpa-afk | 16:40 | |
| *** J1m has joined #zope3-dev | 16:41 | |
| *** eins has quit IRC | 16:44 | |
| philiKON | flox, nice work on the cleanup | 16:50 |
| flox | philiKON: thanks | 16:54 |
| flox | i wonder if i should do cleanup only on trunk... | 16:55 |
| flox | because i do not want totake risk to break somthing... | 16:55 |
| *** Aiste has quit IRC | 16:55 | |
| srichter | flox: I was going to make that suggestion | 16:55 |
| srichter | flox: leave the 3.3 branch as it is; it's stable and jsut needs to get out of the door | 16:55 |
| flox | srichter: ok. i will do non-essential things on trunk only. | 16:56 |
| *** baijum has quit IRC | 17:01 | |
| philiKON | flox, cleanup is never that essential. so yes, trunk is best | 17:02 |
| tlotze | I just found that zope.app.container.browser.adding.Adding.publishTraverse is, well, written a bit less straight-forward than it might be regarding interpretation of the view name. Anyone mind if I straighten it out on the trunk? | 17:05 |
| philiKON | tlotze, well, if the current test coverage is sufficient, it should be fine to refactor it. tests will ensure it still works as expected | 17:15 |
| tlotze | k | 17:16 |
| tlotze | I'll take a look | 17:16 |
| philiKON | of course, you can always ensure that the test coverage is sufficient by writing tests now, then refactor :) | 17:16 |
| philiKON | s/now/first/ | 17:16 |
| tlotze | *g | 17:16 |
| *** jukart has joined #zope3-dev | 17:18 | |
| *** stub has quit IRC | 17:18 | |
| *** whit_ has joined #zope3-dev | 17:18 | |
| srichter | Fielding dissertation: Section 6.3.4 REST Mismatches in HTTP -> Subsection 6.3.4.2 Cookies | 17:20 |
| srichter | :-) | 17:20 |
| *** hdima has quit IRC | 17:25 | |
| Theuni | hmm. can non-persistent components be registered as local utilities? | 17:27 |
| Theuni | i don't care for it to have any persistent state ... | 17:27 |
| philiKON | sure | 17:28 |
| philiKON | but if you register it with a persistent component registry, the comopnent will be pickled as part of the registry | 17:28 |
| philiKON | better to use something like z3c.baseregistry | 17:29 |
| Theuni | hmm. not my use case though. | 17:31 |
| Theuni | not exactly | 17:31 |
| Theuni | thanks anyway | 17:31 |
| srichter | Theuni: what is your use case? | 17:32 |
| srichter | Theuni: because z3c.baseregistry was specifically written to provide a solution to your question | 17:32 |
| Theuni | in general in my case this might be a persistent utility, i just need a demo utility that is not persistent for a while and just wanted to make sure it doesn't break in weird ways | 17:33 |
| Theuni | and out of curiosity | 17:33 |
| srichter | yeah, so that's what you want to do then :-) | 17:34 |
| srichter | register the demo utility in a base registry and add it to your local site | 17:34 |
| srichter | whenever you provide the local version, it will override the demo | 17:35 |
| Theuni | i won't need that probably, because the demo won't be around for long, so i won't need that infrastructure for long | 17:35 |
| Theuni | but i know it's around now | 17:36 |
| Theuni | s/demo/experimental/ | 17:36 |
| philiKON | Theuni, if it's just for demo, just stick it in the global registry | 17:40 |
| philiKON | err , not global | 17:40 |
| philiKON | persistent | 17:40 |
| Theuni | jup | 17:42 |
| *** alecm has joined #zope3-dev | 17:46 | |
| *** batlogg has quit IRC | 17:59 | |
| tlotze | brrr | 18:04 |
| tlotze | Making a deliberate error in my change to Adding doesn't break any tests. | 18:04 |
| tlotze | Looks like there's some functional testing needed... not now. | 18:04 |
| *** tlotze has quit IRC | 18:08 | |
| *** philiKON has quit IRC | 18:10 | |
| *** romanofski has quit IRC | 18:20 | |
| *** ignas has quit IRC | 18:27 | |
| *** whit_ has quit IRC | 18:27 | |
| *** markup_ has joined #zope3-dev | 18:41 | |
| *** zagy has quit IRC | 18:47 | |
| *** dobee has quit IRC | 18:48 | |
| *** hazmat has joined #zope3-dev | 18:51 | |
| *** ChanServ sets mode: +o hazmat | 18:51 | |
| *** gumpa-afk has quit IRC | 18:54 | |
| *** jukart has quit IRC | 19:06 | |
| *** replicant has joined #zope3-dev | 19:06 | |
| *** MJ has quit IRC | 19:07 | |
| *** hazmat has quit IRC | 19:13 | |
| *** zagy has joined #zope3-dev | 19:14 | |
| *** schwendinger has quit IRC | 19:31 | |
| *** schwendinger has joined #zope3-dev | 19:38 | |
| *** dunny has joined #zope3-dev | 19:51 | |
| *** nathany has joined #zope3-dev | 19:53 | |
| *** projekt01 has quit IRC | 19:54 | |
| *** zagy_ has joined #zope3-dev | 20:10 | |
| *** zagy has quit IRC | 20:14 | |
| *** dobee has joined #zope3-dev | 20:22 | |
| *** faassen has joined #zope3-dev | 20:28 | |
| *** kobold has left #zope3-dev | 20:29 | |
| faassen | J1m: when you develop recipes | 20:32 |
| faassen | J1m: how do you test them during development? | 20:32 |
| faassen | J1m: that is, how does buildout find them? | 20:32 |
| faassen | J1m: I'm grasping for some patterns there. | 20:32 |
| *** batlogg has joined #zope3-dev | 20:33 | |
| Theuni | faassen: recipes are eggs and - if i'm not mistaken - will be looked for via easy install | 20:33 |
| faassen | Theuni: where is easy install finding them during development? | 20:33 |
| faassen | there must be some way J1m tested the 3 zope 3 eggs. | 20:34 |
| faassen | together. | 20:34 |
| Theuni | for one at pypi, but if you set 'find-links' in the buildout, it will additionally use those pages as places to look out for | 20:34 |
| faassen | and then fixed bugs in possibly all of them. | 20:34 |
| J1m | faassen: I always develop them as develop eggs. | 20:34 |
| faassen | J1m: how do you pull them together? | 20:34 |
| Theuni | http://svn.zope.org/zc.buildout/trunk/buildout.cfg?rev=69987&view=auto | 20:34 |
| faassen | J1m: you have a directory with 3 develop eggs and such? | 20:34 |
| J1m | Look at zc.buildout. | 20:34 |
| J1m | In buildout.cfg, I have a develop section that names my two egg directories, which have setup.py files. | 20:35 |
| J1m | This causes them to be installed as develop eggs. | 20:35 |
| faassen | J1m: okay, so when you developed the zope 3 eggs, you have a testing buildout somewhere? | 20:35 |
| faassen | J1m: and you check out the 3 eggs into that testing directory? | 20:36 |
| J1m | No | 20:36 |
| J1m | Just a sec. | 20:36 |
| faassen | J1m: sorry, you check out the 3 things from svn. | 20:36 |
| faassen | J1m: and they have setup.py | 20:36 |
| faassen | J1m: I meant to say. | 20:36 |
| *** nathany has quit IRC | 20:37 | |
| faassen | J1m: they're not eggs yet, but they can be installed as develop eggs if you list them under the 'develop' section. | 20:37 |
| J1m | exactly | 20:37 |
| faassen | right, sorry, I just expressed myself badly. | 20:38 |
| faassen | just grasping for patterns here, but I think I see now. | 20:38 |
| J1m | Now most of the zope 3 recipes don't have tests. :( | 20:38 |
| J1m | I should, for each of those projects have tests and a buildout that gives me a test script to run the tests. | 20:39 |
| J1m | The filestorage recipe has some tests, but I ran those tests as part of the zc.sharing buildout. | 20:39 |
| J1m | I really should set up a separate buildout for it. | 20:39 |
| J1m | You could write tests for recipes at two levels: | 20:40 |
| J1m | - Unit level tests are probably easier to write. You provide a faux buildout and make sure that the recipe interacts with it in the right way. | 20:40 |
| J1m | Because the interaction is very simple, this sort of tst is straightforward to write. | 20:41 |
| faassen | you basically just need to provide some parts directory | 20:41 |
| J1m | I experiemented with this for the filestorage recipe tests. | 20:41 |
| faassen | and some options | 20:41 |
| J1m | More or less. | 20:41 |
| J1m | Unfortunately, this sort of test has pretty much zero documentation value. :( | 20:42 |
| J1m | I consider the filestorage recipe tests to be a bit of a failure. | 20:42 |
| J1m | Alternatively, you can write tests that actually run buildout with the recipe. | 20:43 |
| faassen | and then verify whether stuff is actually there. | 20:43 |
| faassen | where you expect it to be. | 20:43 |
| J1m | These tests, have more documentation value, but are much harder to write. | 20:43 |
| J1m | yes | 20:43 |
| faassen | why are they much harder to write? | 20:43 |
| J1m | The zc.recipes.egg and zc.recipes.testrunner tests illustrate this. | 20:44 |
| J1m | Because: | 20:44 |
| J1m | - You end up running programs and capturing output | 20:44 |
| J1m | - Depending on what you're writing, the output can have lots of random content that you have to filter out. | 20:45 |
| faassen | right. | 20:45 |
| J1m | - You need lots of infrastructure, like faux index servers and such. | 20:45 |
| faassen | oh, right. | 20:45 |
| J1m | Although, I suppose that many recipes could be demonstrated in offline mode and avoid a lot of that. | 20:45 |
| J1m | zc.buildout.testintg has a lot of evolved infrastructure to support this. It's not documented. It has what I needed to run the tests in zc.buildout. | 20:46 |
| *** wiggy has joined #zope3-dev | 20:47 | |
| J1m | We probably need something like this for people to use generally. I'm not sure we have enough examples to know what that api should be. | 20:47 |
| J1m | Right now, it's a bit like the early versions of placeful setup. :) | 20:47 |
| *** philiKON has joined #zope3-dev | 20:47 | |
| J1m | I guess soon I need to switch gears and start writing a lot more tests for the recipes I've put together, both to complete them and to refine some testing support infrastructure. | 20:48 |
| *** ianbicking has joined #zope3-dev | 20:50 | |
| *** hazmat has joined #zope3-dev | 20:56 | |
| *** ChanServ sets mode: +o hazmat | 20:56 | |
| faassen | J1m: okay :) | 20:58 |
| *** replicant has quit IRC | 21:01 | |
| *** MJ has joined #zope3-dev | 21:02 | |
| *** gumpa has joined #zope3-dev | 21:27 | |
| *** RaFromBRC has joined #zope3-dev | 21:28 | |
| *** alga has joined #zope3-dev | 21:33 | |
| *** dobee has quit IRC | 21:35 | |
| *** dobee has joined #zope3-dev | 21:41 | |
| *** dobee has quit IRC | 21:43 | |
| *** dunny has quit IRC | 21:45 | |
| *** projekt01 has joined #zope3-dev | 21:51 | |
| *** mkerrin has quit IRC | 21:51 | |
| *** alecm has quit IRC | 21:54 | |
| *** replicant has joined #zope3-dev | 21:58 | |
| *** ktwilight has quit IRC | 21:59 | |
| *** faassen has quit IRC | 21:59 | |
| *** ktwilight has joined #zope3-dev | 22:00 | |
| *** alga_ has joined #zope3-dev | 22:01 | |
| *** alga__ has joined #zope3-dev | 22:06 | |
| *** replicant has quit IRC | 22:07 | |
| *** hazmat has quit IRC | 22:07 | |
| *** alga has quit IRC | 22:14 | |
| *** alga_ has quit IRC | 22:20 | |
| *** alecm has joined #zope3-dev | 22:24 | |
| *** zagy_ has quit IRC | 22:48 | |
| *** timte has quit IRC | 22:56 | |
| *** ignas has joined #zope3-dev | 22:58 | |
| *** ignas has quit IRC | 23:03 | |
| *** gump1 has joined #zope3-dev | 23:14 | |
| *** d2m has quit IRC | 23:18 | |
| *** rocky has quit IRC | 23:21 | |
| *** gumpa has quit IRC | 23:32 | |
| *** Aiste has joined #zope3-dev | 23:41 | |
| *** gump1 has left #zope3-dev | 23:55 | |
| *** rocky has joined #zope3-dev | 23:59 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!