Re: [Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Philipp von Weitershausen wrote: Listen, we were over this. Apparently, some of us are not ;-) (and the problems caused by having two repositories for the same piece of software keep emerging!) I wrote whole proposal about this months ago already [1] and it was disputed heavily. Right, but from what I remember, this was mainly from the Zope 3 crowd, who need beating with a reality stick every so often ;-) doesn't want to go this way. I can tell you we'll have a hard time with the Zope 5 vision already (which I think is the most sensible one at this point). What I'd like to see: - common code base - zope 3 server/publisher/etc components - zope 2 server/publisher/etc components Of course, it'd be great to if they were all interchangeable. Now, if all of zope 3 existing in lib/python/zope (in Zope 2 world) what problems would there by for Zope 3 purists other than a bit of a loss of disk space? Also, put differently, what makes using pure zope 3 compelling over using zope 3 components in Zope 2? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Philipp von Weitershausen wrote: I think that after eggifying Zope 3 in 3.4 and introducing some features in Zope 2.11 that makes us not depend on Zope2isms like Acquisition (while they'd still be available for those who want to use them), we should invest into the Zope 5 vision: explode Zope 3 and make Zope 2 the app server for both worlds, perhaps called Zope 5, perhaps not. Honestly, I think this is leaving it too late. I'd happilly see the two code bases shipped as one release, then at least we wouldn't have the (idiotic to try and explain to someone non-zope) which version of Zope 3 is shipping with this version of Zope 2... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Chris Withers wrote: Philipp von Weitershausen wrote: I think that after eggifying Zope 3 in 3.4 and introducing some features in Zope 2.11 that makes us not depend on Zope2isms like Acquisition (while they'd still be available for those who want to use them), we should invest into the Zope 5 vision: explode Zope 3 and make Zope 2 the app server for both worlds, perhaps called Zope 5, perhaps not. Honestly, I think this is leaving it too late. I'd happilly see the two code bases shipped as one release, then at least we wouldn't have the (idiotic to try and explain to someone non-zope) which version of Zope 3 is shipping with this version of Zope 2... Listen, we were over this. I wrote whole proposal about this months ago already [1] and it was disputed heavily. It's clear that the community doesn't want to go this way. I can tell you we'll have a hard time with the Zope 5 vision already (which I think is the most sensible one at this point). [1] http://dev.zope.org/Zope3/ReuniteZope2AndZope3InTheSourceCodeRepository ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Martin Aspeli wrote: That's 2.10, grep lib/python/zope/interface on your own instance in case it's changed. However, IFoo.providedBy(obj) and IFoo.implementedBy(obj.__class__) should be the same. They are, but when is isImplementedBy going away? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Chris Withers chris at simplistix.co.uk writes: Martin Aspeli wrote: That's 2.10, grep lib/python/zope/interface on your own instance in case it's changed. However, IFoo.providedBy(obj) and IFoo.implementedBy(obj.__class__) should be the same. They are, but when is isImplementedBy going away? Gone in 3.4 http://mail.zope.org/pipermail/zope3-checkins/2006-September/028478.html -- Florent ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Florent Xicluna wrote: Gone in 3.4 http://mail.zope.org/pipermail/zope3-checkins/2006-September/028478.html Any idea which version of Zope 2 that corresponds to? Chris - hey, isn't it time we merged the Zope 2 and Zope 3 code bases? -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.interface.Interface.(isImplementedBy vs implementedBy)
Chris Withers wrote: Florent Xicluna wrote: Gone in 3.4 http://mail.zope.org/pipermail/zope3-checkins/2006-September/028478.html Any idea which version of Zope 2 that corresponds to? 2.11, to be released next year (May or so). Chris - hey, isn't it time we merged the Zope 2 and Zope 3 code bases? *sigh* I think that after eggifying Zope 3 in 3.4 and introducing some features in Zope 2.11 that makes us not depend on Zope2isms like Acquisition (while they'd still be available for those who want to use them), we should invest into the Zope 5 vision: explode Zope 3 and make Zope 2 the app server for both worlds, perhaps called Zope 5, perhaps not. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
