[Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)
Benji York wrote: Roger Ineichen wrote: Is there a way to evolve during the bootstrap process? Or is the manuel process via the ZMI the right way? If min generation is set properly shouldn't this happen automatically? Yes, but is it right way to set min generation == max generation? What do you think,should I remove the _passwordManagerName class attribute, which will break instances in un-evolved databases. I think a generation is too heavy a fix where a simple class attribute will suffice. I like Roger's fix and propose we remove the generation. No, there is also self.password attribute changed to a property which is not so easy to fix without a generation. I see two alternative possibilities: 1. Custom __getstate__() method; 2. The views may use a methods to get/set self.password attribute; -- Dmitry Vasiliev (dima at hlabs.spb.ru) http://hlabs.spb.ru ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)
On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote: I think a generation is too heavy a fix where a simple class attribute will suffice. I like Roger's fix and propose we remove the generation. No, there is also self.password attribute changed to a property which is not so easy to fix without a generation. I see two alternative possibilities: In this case a generation is appropriate. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] New database generation for Zope 3.2 (Was: [Zope3-checkins] Added BBB for older instances)
Stephan Richter wrote: On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote: I think a generation is too heavy a fix where a simple class attribute will suffice. I like Roger's fix and propose we remove the generation. No, there is also self.password attribute changed to a property which is not so easy to fix without a generation. I see two alternative possibilities: In this case a generation is appropriate. Agreed. I didn't know about the other changes. The only thing I would propose would be that the generation be automatically run. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1363 Blamelist: benji_york,srichter BUILD FAILED: failed svn sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
RE: [Zope3-dev] New database generation for Zope 3.2 (Was:[Zope3-checkins] Added BBB for older instances)
Hi Dimitry , Benji and Stephan [...] Stephan Richter wrote: On Saturday 05 November 2005 08:17, Dmitry Vasiliev wrote: I think a generation is too heavy a fix where a simple class attribute will suffice. I like Roger's fix and propose we remove the generation. No, there is also self.password attribute changed to a property which is not so easy to fix without a generation. I see two alternative possibilities: In this case a generation is appropriate. Agreed. I didn't know about the other changes. The only thing I would propose would be that the generation be automatically run. I agree too. I think automatic generation is a good idea in this case. I think a MIGRATION.txt file in the trunk/doc folder would be a good idea for such migration notes. btw, we have to take care on such changes, what's happen if somebody uses allready a password property in a custom class where is inherited form InternalPrincipal? Regards Roger Ineichen Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1364 Blamelist: benji_york BUILD FAILED: failed svn sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Bug in viewmeta.py (page directive handler)
Sven Schomaker wrote: Hi all, I found a tiny bug in the page directive handler page in zope.app.publisher.browser.viewmeta.py. Handling allowed attributes seems to be buggy: SNIP _handle_allowed_attributes(_context, allowed_interface, permission, required) SNAP should most probably be: SNIP _handle_allowed_attributes(_context, allowed_attributes, permission, required) SNAP This seems still to be present in the trunk, so maybe someone with repository access wants to fix this. Please file a collector issue if you think you've found a bug. That way it'll be remembered and won't get lost in mailing list traffic. If you could attach a unified diff with the change you propose, that'd be great. Thanks Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
