IRC log of #zope3-dev for Tuesday, 2008-08-12

*** oggers_ has joined #zope3-dev00:09
*** oggers__ has quit IRC00:13
*** oggers__ has joined #zope3-dev00:14
markusleistok, when i change the default-attribute of the field-instance in update() i can "predefine" some values ...00:15
*** timte has quit IRC00:20
*** oggers_ has quit IRC00:27
*** markusleist has quit IRC00:28
*** whitmo__ is now known as whit00:29
*** alecm has joined #zope3-dev00:39
*** benji has quit IRC00:41
*** jodok_ has joined #zope3-dev00:43
*** jodok has quit IRC00:43
*** sp0cksbeard has quit IRC00:47
*** MJ|out is now known as MJ00:49
*** MJ has quit IRC00:49
*** yotaff has quit IRC00:55
*** greenman has joined #zope3-dev00:56
*** redir has joined #zope3-dev01:00
*** whit has quit IRC01:03
*** whit has joined #zope3-dev01:10
*** lucielejard has quit IRC01:13
*** lurkymclurkleton has quit IRC01:13
*** whit has quit IRC01:17
*** mcdonc has quit IRC01:32
*** mcdonc has joined #zope3-dev01:33
*** flox has left #zope3-dev01:33
*** jodok_ has quit IRC01:34
*** jodok has joined #zope3-dev01:35
*** redir has quit IRC01:50
*** fcorrea has quit IRC01:53
*** oggers__ has quit IRC01:53
*** malthe is now known as malthe|Zzz01:59
*** nathany has quit IRC02:03
*** J1m has quit IRC02:06
*** fcorrea has joined #zope3-dev02:12
*** rmarianski has quit IRC02:14
*** redir has joined #zope3-dev02:22
*** vipod has quit IRC02:26
*** quodt has quit IRC02:32
*** ccomb has quit IRC03:02
*** mcdonc has quit IRC03:19
*** aclark is now known as aclark|away03:20
*** mcdonc has joined #zope3-dev03:23
*** b52laptop has quit IRC03:24
*** tdoggette_ has joined #zope3-dev03:33
*** mcdonc has quit IRC03:50
*** tdoggette has quit IRC03:57
*** mcdonc has joined #zope3-dev04:05
*** srichter has quit IRC04:10
*** whit has joined #zope3-dev04:27
*** deo has joined #zope3-dev04:52
*** ignas has quit IRC05:02
*** elro has quit IRC05:16
*** srichter has joined #zope3-dev05:35
*** redir has quit IRC05:52
*** markusleist has joined #zope3-dev06:01
*** jodok has quit IRC06:03
*** stub has joined #zope3-dev06:05
*** andres has quit IRC06:07
*** ChanServ sets mode: +o srichter06:15
*** fcorrea has quit IRC06:29
*** fcorrea has joined #zope3-dev06:31
*** brandon_rhodes has quit IRC07:05
*** binseer has joined #zope3-dev07:20
*** greenman has quit IRC07:41
*** BjornT has joined #zope3-dev07:43
*** philiKON_ has joined #zope3-dev07:53
*** philiKON has quit IRC08:01
*** kursor has joined #zope3-dev08:08
*** binseer has quit IRC08:09
*** stub has quit IRC08:10
*** markusleist has quit IRC08:11
*** jodok has joined #zope3-dev08:17
*** jodok has quit IRC08:18
*** binseer has joined #zope3-dev08:25
*** timte has joined #zope3-dev08:28
*** philiKON_ has quit IRC08:32
*** philiKON has joined #zope3-dev08:59
*** __mac__ has joined #zope3-dev09:03
*** fairwinds has quit IRC09:13
*** srichter has quit IRC09:26
*** jayaraj has joined #zope3-dev09:35
*** greenman has joined #zope3-dev09:36
*** greenman has quit IRC09:51
*** Theuni has left #zope3-dev09:52
*** srichter has joined #zope3-dev09:54
*** ChanServ sets mode: +o srichter09:54
*** __mac___ has joined #zope3-dev09:56
*** malthe|Zzz is now known as malthe09:58
*** philiKON has quit IRC09:59
*** philiKON has joined #zope3-dev10:00
*** srichter has quit IRC10:05
*** srichter has joined #zope3-dev10:06
*** agroszer has joined #zope3-dev10:09
*** __mac__ has quit IRC10:13
*** malthe has quit IRC10:20
*** MJ|nickcollision has joined #zope3-dev10:20
*** MJ|nickcollision is now known as MJ10:21
*** Theuni has joined #zope3-dev10:22
*** yvl has joined #zope3-dev10:25
*** tarek has joined #zope3-dev10:25
*** quodt has joined #zope3-dev10:25
*** srichter has quit IRC10:27
*** mcdonc has quit IRC10:34
*** ignas has joined #zope3-dev10:41
*** jayaraj_ has joined #zope3-dev10:44
*** binseer_ has joined #zope3-dev10:44
*** markusleist has joined #zope3-dev10:44
*** flox has joined #zope3-dev10:55
*** MJ has quit IRC10:59
*** binseer has quit IRC11:02
*** jayaraj has quit IRC11:02
*** greenman has joined #zope3-dev11:03
*** MJ has joined #zope3-dev11:07
*** junkafarian has joined #zope3-dev11:07
*** srichter has joined #zope3-dev11:12
*** afd__ has joined #zope3-dev11:14
*** maurits has joined #zope3-dev11:23
*** malthe has joined #zope3-dev11:24
*** alecm has quit IRC11:27
*** elro has joined #zope3-dev11:31
*** elro has quit IRC11:33
*** jodok has joined #zope3-dev11:40
*** jayaraj_ has quit IRC11:44
*** binseer_ has quit IRC11:45
*** jodok has quit IRC11:49
*** jodok has joined #zope3-dev11:49
*** junkafarian has quit IRC11:55
*** aclark|away is now known as aclark12:02
*** binseer_ has joined #zope3-dev12:02
*** jayaraj_ has joined #zope3-dev12:03
*** mustap has joined #zope3-dev12:05
*** redir has joined #zope3-dev12:11
*** elro has joined #zope3-dev12:13
*** sunew has joined #zope3-dev12:13
*** jodok_ has joined #zope3-dev12:16
*** jodok has quit IRC12:17
*** ktwilight_ has joined #zope3-dev12:21
*** jodok has joined #zope3-dev12:29
*** jodok_ has quit IRC12:29
*** ktwilight has quit IRC12:34
*** MrTopf has joined #zope3-dev12:38
*** pyqwer has joined #zope3-dev12:44
*** pyqwer has left #zope3-dev12:45
*** baijum has joined #zope3-dev12:47
*** andres has joined #zope3-dev12:59
*** jodok_ has joined #zope3-dev13:00
*** jodok_ has quit IRC13:08
*** jodok_ has joined #zope3-dev13:09
*** jodok has quit IRC13:13
*** jodok_ has quit IRC13:23
*** jodok has joined #zope3-dev13:23
*** alga has joined #zope3-dev13:29
*** baijum has quit IRC13:31
*** jodok_ has joined #zope3-dev13:34
*** jodok has quit IRC13:35
*** tdoggette__ has joined #zope3-dev13:35
*** b52laptop has joined #zope3-dev13:35
*** MJ is now known as MJ|lunch13:39
*** sunew has quit IRC13:41
*** thruflo has joined #zope3-dev13:44
*** dirceu has joined #zope3-dev13:45
*** dunny has quit IRC13:59
*** tdoggette_ has quit IRC14:00
*** elro has quit IRC14:04
*** philiKON has quit IRC14:04
*** __mac___ has quit IRC14:04
*** SteveA has quit IRC14:04
*** elro has joined #zope3-dev14:04
*** philiKON has joined #zope3-dev14:04
*** __mac___ has joined #zope3-dev14:04
*** SteveA has joined #zope3-dev14:04
*** MJ|lunch is now known as MJ14:05
*** yotaff has joined #zope3-dev14:08
*** tdoggette__ has quit IRC14:10
*** dirceu has quit IRC14:20
*** projekt01 has joined #zope3-dev14:25
*** afd___ has joined #zope3-dev14:30
*** redir has quit IRC14:30
*** andres_f has joined #zope3-dev14:34
*** andres has quit IRC14:38
*** redir has joined #zope3-dev14:40
*** redir has quit IRC14:42
*** afd__ has quit IRC14:44
*** kursor has quit IRC14:47
*** jodok_ has quit IRC14:48
*** brandon_rhodes has joined #zope3-dev15:05
*** afd__ has joined #zope3-dev15:06
*** J1m has joined #zope3-dev15:07
*** sunew has joined #zope3-dev15:09
*** greenman has quit IRC15:09
*** afd___ has quit IRC15:11
*** benji has joined #zope3-dev15:24
*** benji is now known as Guest8722815:25
*** fairwinds has joined #zope3-dev15:26
*** Guest87228 has quit IRC15:35
*** benji has joined #zope3-dev15:35
*** benji is now known as Guest7818615:36
*** Guest78186 is now known as benji15:37
*** benji has quit IRC15:38
*** benji has joined #zope3-dev15:38
*** J1m has quit IRC15:42
*** jodok has joined #zope3-dev15:49
*** lurkymclurkleton has joined #zope3-dev15:56
*** afd__ has quit IRC16:02
*** srichter has quit IRC16:11
yotaffhow use multiple buildout.cfg on one package ?16:18
yotaffdon't find any options for the config file selection,16:19
ignas-c ?16:19
*** ignas has quit IRC16:19
*** regebro has joined #zope3-dev16:20
philiKONon one package?16:22
philiKONa buildout is a buldout16:22
philiKONa buildout is a directory with a buildout.cfg16:22
philiKONfeel free to create as many directories and buildout.cfg's in them as you want ;)16:22
*** sp0cksbeard has joined #zope3-dev16:23
*** jayaraj_ has quit IRC16:23
*** jayaraj has joined #zope3-dev16:26
*** J1m has joined #zope3-dev16:26
*** philiKON has quit IRC16:27
*** afd__ has joined #zope3-dev16:28
tarekyotaff, take a look at I don't know what is its state, but it has already useful things16:30
yotaff-c is fine :)16:31
*** charith_para has joined #zope3-dev16:35
*** jodok_ has joined #zope3-dev16:48
*** jodok has quit IRC16:49
chaoflowis there some trick, that a test_suite() in is found, when running ./bin/test -f? mine is not found16:57
*** malthe has quit IRC16:59
*** srichter has joined #zope3-dev17:01
benjichaoflow: is it found when you just run bin/test with no options?17:03
chaoflowit just finds a unit test from tests.py17:05
chaoflowi put an import pdb;pdb.set_trace() directly into the - the file does not get loaded at all17:06
benjitry running bin/test --tests-pattern [fn]?tests17:06
benji(although, I though that was the default)17:07
chaoflowbenji: that did something :) now its complaining about a missing ftesting.zcml17:10
*** deo has quit IRC17:10
chaoflowI put it in the root of my buildout, it seems to expect it in parts/test/ftesting.zcml17:10
benjiit should be in the same directory as the file17:11
benjioh, and there's no reason to name your test files any more, you can just use tests.py17:11
chaoflowbenji: i will still be able to seperately run unittests and functional tests?17:12
*** mcdonc has joined #zope3-dev17:12
chaoflowbenji: thx - last question I just answered myself17:15
*** pyqwer has joined #zope3-dev17:17
*** pyqwer has left #zope3-dev17:18
fairwindsJ1m:  I would like to trigger the uninstall/update of another part of a buildout when a part is updated to have a cascade effect - so both parts get updated. I want to trigger this from a custom cmmi recipe using its update method to handle updating where a dependency exists on another part that uses a cmmi recipe. Effect would be both parts get uninstalled and recompiled based on ordering of parts. Can you suggest an approach? In a nutsh17:18
chaoflowthe problem remains with the ftesting.zcml: it is looking for paula.authentication/parts/test/ftesting.zcml, and I have paula.authentication/src/paula/authentication/ftesting.zcml and before paula.authentication/ftesting17:19
J1mfairwinds, the best you can do is reflect the change in options. Have the dependent part read an option that changes when the depended upon part changes.17:20
J1mI kind of doubt that this fits your use case though.17:20
J1mor maybe it does -- I'm not sure.17:20
fairwindshmm. that might do it17:21
fairwindsI think thats a possibility I'll give this a go. thanks J1m17:22
*** alecm has joined #zope3-dev17:29
*** tarek has quit IRC17:30
*** malthe has joined #zope3-dev17:30
*** tarek has joined #zope3-dev17:31
*** srichter has quit IRC17:34
*** srichter has joined #zope3-dev17:34
*** philiKON has joined #zope3-dev17:36
*** tdoggette has joined #zope3-dev17:38
*** lucielejard has joined #zope3-dev17:38
*** mustap has left #zope3-dev17:43
fairwindsJ1m: Another thought on this. Was wondering if I might do this by manipulating .installed.cfg. Will removing the dependent part from the .installed.cfg cause it to become uninstalled? Could do something like this with regex if this is a possibility.17:52
*** rmarianski has joined #zope3-dev17:52
*** MJ has quit IRC17:54
*** strichter has joined #zope3-dev17:55
*** andres_f has quit IRC17:57
*** srichter has quit IRC17:57
fairwindsJ1m: if something like that could work I could put this in my cmmi update method17:58
fairwindsguess i could try something here too17:59
*** sunew has quit IRC18:03
*** quodt has quit IRC18:04
*** afd__ has quit IRC18:07
*** ktwilight_ has quit IRC18:11
*** timte has quit IRC18:11
*** ktwilight_ has joined #zope3-dev18:12
*** projekt01 has quit IRC18:15
*** jodok has joined #zope3-dev18:19
*** reco has joined #zope3-dev18:19
*** jodok_ has quit IRC18:20
J1mfairwinds, you shouldn't try to much with .installed.cfg. This is owned by buildout.  Touching it voids your warranty.18:24
J1mI suspect that yopur use case wants a new buildout feature.18:25
fairwindsyeah probably18:25
J1mI had a similar use case in the past and didn't have time at the time to come up with a good model for it.18:26
* J1m wonders how that is cool18:26
J1mMy use case was a part that read a file created by another part.18:27
fairwindswell, its nice to know that I am not alone here ;-)18:27
benjiwould it be possible to create a "dependency" recipe that takes multiple other recipes as parameters and generates this behavior18:27
J1mI ended up rethinking my problem to avoid the use case.18:27
J1mbenji, I have no idea :)18:28
fairwindshey benji: Is there anything similar to this right now in the recipe spectrum?18:29
J1mRight now, dependency is implicit through options.18:29
benjifairwinds: not that I know of18:30
J1mIt might make sense to allow dependencies to be expressed explicitly.18:30
fairwindsyes. I would like that.18:30
fairwindswhat i was thinking of including dependencies in my cmmi recipe. If part changes, want those to be looked up18:31
J1mso a part would get (re)installed whenever a part it explicitly depends on is reinstalled.18:31
fairwindsuh huh18:32
J1malthough something simpler might work too.18:32
fairwindslike what?18:32
J1mfor example, if the buildout data structure recorded what was done with a part and another part could read that, then the dependent part could use that information to decide what to do.18:33
J1mso, suppose A depends on B.  It reads an option from B, so B is processed first.  When A runs, it reads buildout['buildout18:34
fairwindssure. I guess thats where i was coming from with .installed since state is currently recorded there18:34
J1mgaaa sorry, try again...18:34
J1mso, suppose A depends on B.  It reads an option from B, so B is processed first.  When A runs, it reads buildout['B']['__buildout_installed__'] to decide whether B was reinstalled.18:35
J1mIt might do more or less processing based on that.18:35
J1mBut even that might not be enough. After all, C might depend on A and want to base it's decisions on what A actually did.18:36
*** alecm has quit IRC18:36
J1mOne almost wants a more generic mechanism for parts to record data during install/update that dependent parts can read to decide what to do.18:37
fairwindsmy thought was to look for the dependency in all installed parts and uninstall them all18:37
J1manyway, no obvious (to me) right answer.18:37
*** jodok has quit IRC18:38
TheuniJ1m: yeah. I had the issue of wanting to read another's part data without influencing the dependency graph too18:38
*** jodok has joined #zope3-dev18:38
J1mI dount that installed.cfg would give you enough info.18:38
TheuniI think I got away at restructuring the buildout at that time.18:38
fairwindssince ordering of parts would facilitate installation in correct order18:39
*** hazmat has quit IRC18:39
chaoflowwhen the utility zcml directive is not found in a FunctionalDocFileSuite, what might I be doing wrong?18:39
*** MJ has joined #zope3-dev18:40
J1mHm, maybe A should read B's __buoldout_signature__.18:40
J1mThan any change in B would trigger a change in A.18:40
J1mIt may be that __buoldout_signature__ isn't available soon enough, but it probably could be without much effort.18:41
J1mThat would work when changes are driven soley by configuration.18:42
fairwindsand everything already in .configure.cfg18:43
fairwindssorry .installed.cfg?18:44
J1mwhich is more or less the same thing.18:44
J1mexcept for mechanism.18:45
fairwindsbrain fart - to much configuration language symptoms :-)18:45
J1mso, if __buildout_signature__ can be read by a part's initializer (or in the configuration), that should be enough, I think.18:46
fairwindsshould this be part of buildout or recipe method18:47
*** jodok_ has joined #zope3-dev18:47
J1mHm, or maybe not.18:47
J1mMaybe __buildout_signature__ isn't enough.18:47
J1mI'm a little rusty on what that is.18:48
J1mBasically, you want some sort of hash of the other parts uptions.18:48
fairwindsthat would be good yes18:48
J1mI think buildout could provide an option that could be read that reflects the configuration of a part that one depends on.18:49
J1mThen again, it might be better ro express this as an explicit dependency, even if it uses this mechanism under the hood.18:49
fairwindsi like the notion of an explicit dependency18:50
*** rocky has quit IRC18:50
*** jodok has quit IRC18:50
J1mWe'd need to decide how to spell it.18:51
J1mYou can think about that while I get back to work (or get lunch)18:51
*** rocky has joined #zope3-dev18:53
*** timte has joined #zope3-dev18:53
*** __mac___ has quit IRC18:54
*** __mac__ has joined #zope3-dev18:55
*** reco has quit IRC18:55
*** alecm has joined #zope3-dev18:57
*** binseer_ has quit IRC19:00
chaoflowin ftesting.zcml I register a utility. I include to get a utility directive. However, in a FunctionalDocFileSuite, I get a ComponentLookupError, when trying to getUtility(). any ideas?19:07
philiKONdid you say19:08
philiKONsuite.layer = YourZCMLBasedLayer19:08
philiKONftesting.zcml won't be loaded automagically you know19:08
*** alga has quit IRC19:10
chaoflowphiliKON: I took the layer things from a zopeproject generated ftesting.zcml. The file is loaded, at least I got errors from it19:10
philiKONwell, then i don't know19:11
*** sunew has joined #zope3-dev19:12
chaoflowphiliKON: are there any includes that need to be present in ftesting for the component registry to work?19:13
philiKONif you're using the stuff from zopeproject, it should work19:14
J1mfairwinds, so you can probably try this out by writing a recipe that takes a set of parts and conputes a hash based on the part items and makes the hash available for other parts to read.  This would allow you to prototype the idea and make sure that it actually solves your problem. (I assume that this is what benji was hinting at.)19:14
fairwindshi ya. yes I can do this. Another thought . Recipe handles this somewhat currently. If recipe is changed all parts depending on recipe are uninstalled. What is mechanism there?19:17
chaoflowphiliKON: thx, will have a look, what I am missing from it19:17
*** MJ is now known as MJ|afk19:18
*** J1m has quit IRC19:20
*** maurits has left #zope3-dev19:21
*** alga has joined #zope3-dev19:21
*** jayaraj has quit IRC19:22
*** djohnson has joined #zope3-dev19:29
*** djohnson has left #zope3-dev19:29
*** sm has quit IRC19:35
*** sm has joined #zope3-dev19:35
*** jodok_ has quit IRC19:45
*** mintsauce has joined #zope3-dev19:46
mintsauceAre there any existing Paypal/Google Checkout/Etc payment components for Zope 3?19:47
*** ccomb_ has quit IRC19:48
*** J1m has joined #zope3-dev19:49
*** MJ|afk has quit IRC19:50
*** hazmat has joined #zope3-dev19:54
*** ChanServ sets mode: +o hazmat19:54
*** sunew has quit IRC19:58
*** hazmat has quit IRC20:00
*** replicant has joined #zope3-dev20:01
*** tarek has quit IRC20:07
*** replicant has quit IRC20:07
*** thruflo has quit IRC20:09
*** replicant has joined #zope3-dev20:11
*** tdoggette has quit IRC20:18
*** tarek has joined #zope3-dev20:24
*** ccomb has joined #zope3-dev20:30
*** markusleist has quit IRC20:33
*** timte has quit IRC20:33
*** whit has quit IRC20:37
*** replaceafill has joined #zope3-dev20:39
*** rocky has quit IRC20:41
*** rocky has joined #zope3-dev20:43
*** baijum has joined #zope3-dev20:49
*** whit has joined #zope3-dev20:55
*** whit has quit IRC20:56
*** whit has joined #zope3-dev20:56
*** whitmo has joined #zope3-dev20:59
*** whit has quit IRC21:00
*** replaceafill has left #zope3-dev21:03
*** whitmo has quit IRC21:05
*** jsadjohnson has left #zope3-dev21:05
*** sunew has joined #zope3-dev21:06
*** whit has joined #zope3-dev21:12
*** pyqwer has joined #zope3-dev21:16
*** pyqwer has quit IRC21:23
*** charith_para has quit IRC21:28
*** sunew has quit IRC21:32
*** MrTopf has quit IRC21:34
*** MrTopf has joined #zope3-dev21:36
fairwindsJ1m: Have been thinking more sort of solidifying ideas about this. I think what needs to happen is that we need a .dependencies.cfg for explicit dependencies. Buildout would generate a md5sum from text of each part. This needs to occur in buildout before the configuration is read so that buildout will respond to options changes. So you are able to use dependency information in options. example. dependency = ${dependency:python25}, or anyt21:45
*** agroszer_ has joined #zope3-dev21:46
fairwindsdependencies.cfg would look like [dependency]  python25 =21:47
fairwindspython25 = afb5451049eda91fbde10bd5a4b7fadc21:48
fairwindssomepart = someothermd521:48
*** vipod has joined #zope3-dev21:53
fairwindsJ1m: This can't all be done in a recipe without being sort of lame. For example, you make a recipe that generates the md5sum but would it would have to be run each time before a buildout because we need the dependency.cfg for options uninstall to be triggered. To be efficient it would need to be part of buildout probably with an arg since many would not need this feature necessarily.21:54
*** replicant has quit IRC21:58
*** agroszer has quit IRC22:00
*** ARiKA has quit IRC22:01
*** markusleist has joined #zope3-dev22:01
*** baijum has left #zope3-dev22:04
*** hazmat has joined #zope3-dev22:05
*** ChanServ sets mode: +o hazmat22:05
*** sm has quit IRC22:07
*** supton has joined #zope3-dev22:07
*** afd__ has joined #zope3-dev22:12
*** MrTopf has quit IRC22:17
fairwindsJ1m:  In meantime I will write a recipe that has a script to generate the dependencies.cfg prior running  buildout just as example22:25
J1mfairwinds, I didn't see your earlier messages.22:27
fairwindsoh ok let me redo22:28
J1mI don't see the point of .dependencies.cfg.22:28
fairwindsI think what needs to happen is that we need a .dependencies.cfg for explicit dependencies. Buildout would generate a md5sum from text of each part. This needs to occur in buildout before the configuration is read so that buildout will respond to options changes. So you are able to use dependency information in options. example. dependency = ${dependency:python25}, or anything = {dependency:somepart}.  So lets say for python example, you22:28
J1mall you need is for a dependeont part to include, in it's options, a hash of the options of it's dependencies.22:29
J1mThis can be fairly easily arranged without a new config file.22:29
J1mno, you are mistaken.22:29
J1mIt's much simpler than you think it is.22:30
*** elro has quit IRC22:30
*** yotaff has quit IRC22:30
J1mDependencies should be part of the part definition itself.22:30
J1mSomething like:22:30
J1mdepends-on: b, c22:30
J1mrecipe = ...22:31
J1mThere shouldn't be a separate file.22:31
J1munder the hood, buildout will simple include a special option in a who's value is the hash of b & c's options.22:31
J1mThen the existing machinery for deciding when to reinstall will work just fine.22:32
fairwindsok sure22:32
J1mAs I mentioned earlier, it should be possible to prototyoe this now using a helper recipe.22:33
J1mIn the long term, the biggest issue, aside from implementation, is deciding what the new option name should be, since it would have to be a reserved name (like recipe).22:33
fairwindsok i understand. what i was suggesting was another way to do it but with a file22:37
*** aclark is now known as aclark|away22:42
fairwindsthis helper recipe, we just store info in a config file temporarily?22:43
*** jodok has joined #zope3-dev22:45
fairwindsJ1m: depends-on seems fine to me22:50
*** dunny has joined #zope3-dev22:50
J1mI'm incined to pick something more obnoxious -- to reduce the possibility of breakage.22:52
fairwindshow obnoxious?22:52
J1mI dunno :)22:54
* benji suggests "snarglefloop"22:54
* J1m likes it22:54
*** hazmat has quit IRC23:14
*** quodt has joined #zope3-dev23:18
*** greenman has joined #zope3-dev23:30
*** greenman has quit IRC23:30
*** fairwinds has quit IRC23:32
*** mintsauce has quit IRC23:36
*** regebro has quit IRC23:39
*** agroszer_ has quit IRC23:40
*** Jell-O-Fishi has joined #zope3-dev23:42
*** alga has quit IRC23:43
*** vipod has quit IRC23:46
*** fairwinds has joined #zope3-dev23:52
*** timte has joined #zope3-dev23:53
*** supton has quit IRC23:55

Generated by 2.15.1 by Marius Gedminas - find it at!