Hey,
I've released our changes in zope.app.intid. We hadn't touched
zope.app.catalog and zope.app.keyreference.
Anyway, the trunks are yours.
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
2009/1/31 Martijn Faassen :
> Dan Korostelev wrote:
>> Well, I chose packages that are kind of separated from most of "zope
>> the application" packages, because there aren't many packages that
>> depend on either zope.app.catalog or zope.app.intid/keyreference. So I
>> think we can do that work at
Hey,
Dan Korostelev wrote:
> Well, I chose packages that are kind of separated from most of "zope
> the application" packages, because there aren't many packages that
> depend on either zope.app.catalog or zope.app.intid/keyreference. So I
> think we can do that work at the same time. However, it
Hi,
On Sat, 31 Jan 2009 15:11:44 +0300
Dan Korostelev wrote:
> 2009/1/31 Christian Theune :
> > WRT the ZODB issues: I've started working on a 'touch' tool for ZODB
> > that analyzes (pickle-based) storages for class references which are
> > missing in your code base and (if all class references
2009/1/31 Christian Theune :
> WRT the ZODB issues: I've started working on a 'touch' tool for ZODB
> that analyzes (pickle-based) storages for class references which are
> missing in your code base and (if all class references exist) can touch
> all objects that reference classes from indirect imp
Hey,
[snip plan to clean up more dependencies]
Awesome! As Christian said, this is pretty much what we've been doing.
You might want to mess around with z3c.recipe.compattest to run
compatibility tests after your changes, though it's still a bit finicky
and rather slow. But if you try it out,
Hi,
On Sat, 31 Jan 2009 13:59:52 +0300
Dan Korostelev wrote:
> While you guys are moving zope.app.container to zope.container and
> those cleaning many dependencies, I'd also like to clean intid/catalog
> related stuff. The whole thing consists of three main packages that
> can be cleaned:
>
>
