Hi, to get generations working in Zope 2 the following subscriber is needed: @zope.component.adapter(zope.app.appsetup.IProcessStartingEvent) def evolve_minimum(event): zope.app.generations.generations.evolve( Zope2.DB, zope.app.generations.generations.EVOLVEMINIMUM) I think should become part of Zope 2 / Five. Objections? Regards, -- Christian Zagrodnick · cz@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Tue, Dec 15, 2009 at 11:02, Christian Zagrodnick <cz@gocept.com> wrote:
Hi,
to get generations working in Zope 2 the following subscriber is needed:
@zope.component.adapter(zope.app.appsetup.IProcessStartingEvent) def evolve_minimum(event): zope.app.generations.generations.evolve( Zope2.DB, zope.app.generations.generations.EVOLVEMINIMUM)
I think should become part of Zope 2 / Five. Objections?
Not really, but by making it a part of Five you make any use of generations dependant on having at least that version of Five. If that's OK for you, then no objections. The alternative would be a separate production but admittedly, having a separate product just to register single-line adapter seems silly. :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
On 12/15/09 11:02 , Christian Zagrodnick wrote:
Hi,
to get generations working in Zope 2 the following subscriber is needed:
@zope.component.adapter(zope.app.appsetup.IProcessStartingEvent) def evolve_minimum(event): zope.app.generations.generations.evolve( Zope2.DB, zope.app.generations.generations.EVOLVEMINIMUM)
I think should become part of Zope 2 / Five. Objections?
-1, this would add a needless dependency on zope.app.generations to Zope 2 as far as I can see. Why not move include this in zope.app.generations itself in a [zope2] extra ? Or create a tiny five.generations package to do this. Wichert.
On Tue, Dec 15, 2009 at 11:20, Wichert Akkerman <wichert@wiggy.net> wrote:
-1, this would add a needless dependency on zope.app.generations to Zope 2 as far as I can see.
Good point. The lack of imports tricked me into thinking this was easier than it was. :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64
On 2009-12-15 11:20:19 +0100, Wichert Akkerman <wichert@wiggy.net> said:
On 12/15/09 11:02 , Christian Zagrodnick wrote:
Hi,
to get generations working in Zope 2 the following subscriber is needed:
@zope.component.adapter(zope.app.appsetup.IProcessStartingEvent) def evolve_minimum(event): zope.app.generations.generations.evolve( Zope2.DB, zope.app.generations.generations.EVOLVEMINIMUM)
I think should become part of Zope 2 / Five. Objections?
-1, this would add a needless dependency on zope.app.generations to Zope 2 as far as I can see. Why not move include this in zope.app.generations itself in a [zope2] extra ? Or create a tiny five.generations package to do this.
five.generations is "part of five" enough for me ;) I don't like an zope2 extra for zope.app.generations. -- Christian Zagrodnick · cz@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development
participants (3)
-
Christian Zagrodnick -
Lennart Regebro -
Wichert Akkerman