[Zope-dev] Re: Splitting up zope.app.container
On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said: The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces. If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions. Is it package overkill to move these out to, say, zope.container? +1 Also the container interfaces could be moved there. -- Christian Zagrodnick gocept gmbh co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Splitting up zope.app.container
On 16.04.2008, at 18:34, Malthe Borch wrote: The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces. If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions. Is it package overkill to move these out to, say, zope.container? hi malthe +1 good idea what we need most ist zope.app.container.interfaces.IContained and the proxies \malthe ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- Lovely Systems, senior developer phone: +43 5572 908060, fax: +43 5572 908060-77 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria skype: bernd.dorn smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
AW: [Zope-dev] Re: Splitting up zope.app.container
Hi Christian Betreff: [Zope-dev] Re: Splitting up zope.app.container On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said: The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces. If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions. Is it package overkill to move these out to, say, zope.container? +1 Also the container interfaces could be moved there. +1 Regards Roger Ineichen -- Christian Zagrodnick gocept gmbh co. kg . forsterstrasse 29 . 06112 halle/saale www.gocept.com . fon. +49 345 12298894 . fax. +49 345 12298891 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
Hi. I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. Scope: For those unfamiliar with the branch, it makes Acquisition aware of __parent__ pointers. This makes it unnecessary to use Acquisition mixin's for Zope 3 code to use them in Zope 2 code. The security machinery of Zope 2 will still be able to work as expected. Status: All tests in the Zope itself pass. New tests have been written for all edge cases found during the development of the branch. As a real world exposure Plone has been used to test the branch. All tests in Plone except one edge-case of a monkey-patch loaded package still pass. Plone in current versions make heavy use of Zope 3 and Five technologies inside Zope 2, so I see this as a very good indicator for the readiness of the branch. The one edge-case is something which needs to be fixed in Plone, as it doesn't make use of any official API. Risks: Using Zope 3 code inside Zope 2 has lead to various 'inventive solutions' to work around problems. Some of these have not used official API's. It is possible that some of those might need to be adjusted. Adjusting them should be straight forward in most cases and mostly consist of removing the hackish workarounds. The second problem that might arise, is that the implicit assumption that every object inside Zope 2 inherits from Acquisition base classes no longer holds. Code that relies on the various aq_* attributes to be there need to be adjusted to use the Acquisition methods instead. This change is trivial to do and doesn't need to be done at first. It only needs to be done when you want to allow direct Zope 3 code in your application. As part of the branch all code in Zope 2 itself have been adjusted to use the aq_* methods. Timeline: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? Hanno P.S. Thanks to philiKON for doing most of the work on this branch :) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: AQ-Parent branch test failues was: Re: Five and browser-oriented components
Philipp von Weitershausen wrote: Wichert Akkerman wrote: Previously Philipp von Weitershausen wrote: In my opinion, the fact that it accidentally worked as an instance variable isn't a very strong argument for continuing to support it. To me, this is a prime example of misusing a Five component which now leads to problems when we go pure Zope3. I'ld agree if there was a docstring or interface that made that explicit. I've updated the relevant code in plone.app.portlets though since the change is harmless. Cool, that's great. If this is just a matter of a docstring, I'm sure that can be arranged :) I added a docstring on the branch now. If we get approval for the branch merge in the current form (see new thread) I'll backport the docstring to all current active branches. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote: On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? +sys.maxint! Darn. My +1 won't fit in there anymore! -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Christian Theune wrote: On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote: On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? +sys.maxint! Darn. My +1 won't fit in there anymore! perhaps martijn's still on 32-bit? :) anyway, +1 from me as well. andi -- zeidler it consulting - http://zitc.de/ - [EMAIL PROTECTED] friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.1rc1 released! -- http://plone.org/products/plone/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
Previously Martijn Pieters wrote: On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? +sys.maxint! I'm afraid any further +1s will turn that into a negative score now. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Wed Apr 16 11:00:00 2008 UTC to Thu Apr 17 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Apr 16 21:00:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009415.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 16 21:02:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009416.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 16 21:03:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009417.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 16 21:05:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009418.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Apr 16 21:06:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009419.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
On Apr 17, 2008, at 12:27 , Hanno Schlichting wrote: Opinions, votes? +1 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? +sys.maxint! Thanks, Hanno, for carrying this to it's completion! -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
--On 17. April 2008 12:27:42 +0200 Hanno Schlichting [EMAIL PROTECTED] wrote: Hi. I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. Go ahead. Andreas pgphIV5gzoW65.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Hanno Schlichting wrote: Timeline: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. This sounds good. Here's another idea, though: In accordance with release early and often, how about scheduling the 2.12 release shortly after the 2.11 one? So the only new thing in 2.12 would be the philikon-aq branch (it would still ship with the same Zope 3 libraries as 2.11, etc.). Opinions, votes? +1 :) P.S. Thanks to philiKON for doing most of the work on this branch :) And thanks to Hanno for testing it against Plone and making lots of improvements! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Five and browser-oriented components
Hanno Schlichting wrote: Martijn Faassen wrote: Alexander Limi wrote: On Mon, 14 Apr 2008 10:11:11 -0700, Philipp von Weitershausen [EMAIL PROTECTED] wrote: *IF* you'd like to be pragmatic, I'd suggest we clean up those failing Plone tests, merge the branch and be on our way. This gets back to Hanno's suggestion of writing a clean test case that demonstrates this problem. We can then get it into Zope and fix it. This should allow cleaning up the Zope 3 integration in Zope 2 significantly. I kept my promise and added the simple tests for the first two issues I found while doing testing against Plone. Excellent, thank you very much! I hope this will motivate people to look into this branch again. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Splitting up zope.app.container
Bernd Dorn wrote: On 16.04.2008, at 18:34, Malthe Borch wrote: The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces. If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions. Is it package overkill to move these out to, say, zope.container? hi malthe +1 good idea what we need most ist zope.app.container.interfaces.IContained and the proxies +1 I support this move as well. We just need to be careful not to move any content that can be persisted. Regards, Martijn P.S. Thanks for bringing up topics on the mailing list like this Malthe, I think that's a really good initiative! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Hey, Hanno, this is a major step forward! +1 from me as well. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
On 17.04.2008, at 12:27, Hanno Schlichting wrote: Opinions, votes? +1 -- Stefan H. Holek [EMAIL PROTECTED] ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Previously Philipp von Weitershausen wrote: This sounds good. Here's another idea, though: In accordance with release early and often, how about scheduling the 2.12 release shortly after the 2.11 one? So the only new thing in 2.12 would be the philikon-aq branch (it would still ship with the same Zope 3 libraries as 2.11, etc.). +1 Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Philipp von Weitershausen wrote: Hanno Schlichting wrote: Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. This sounds good. Here's another idea, though: In accordance with release early and often, how about scheduling the 2.12 release shortly after the 2.11 one? So the only new thing in 2.12 would be the philikon-aq branch (it would still ship with the same Zope 3 libraries as 2.11, etc.). I suspect we want to do something about the eggification story of Zope 2 for Zope 2.12 as well. Figuring out the approach and documenting it might take some additional time. I don't see that releasing another Zope 2.13 shortly after 2.12 makes a lot of sense. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Hi. I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. Scope: For those unfamiliar with the branch, it makes Acquisition aware of __parent__ pointers. This makes it unnecessary to use Acquisition mixin's for Zope 3 code to use them in Zope 2 code. The security machinery of Zope 2 will still be able to work as expected. Status: All tests in the Zope itself pass. New tests have been written for all edge cases found during the development of the branch. As a real world exposure Plone has been used to test the branch. All tests in Plone except one edge-case of a monkey-patch loaded package still pass. Plone in current versions make heavy use of Zope 3 and Five technologies inside Zope 2, so I see this as a very good indicator for the readiness of the branch. The one edge-case is something which needs to be fixed in Plone, as it doesn't make use of any official API. Risks: Using Zope 3 code inside Zope 2 has lead to various 'inventive solutions' to work around problems. Some of these have not used official API's. It is possible that some of those might need to be adjusted. Adjusting them should be straight forward in most cases and mostly consist of removing the hackish workarounds. The second problem that might arise, is that the implicit assumption that every object inside Zope 2 inherits from Acquisition base classes no longer holds. Code that relies on the various aq_* attributes to be there need to be adjusted to use the Acquisition methods instead. The major downside here is that restricted code doesn't have access to the required functions ('aq_inner', 'aq_parent', 'aq_acquire'), and hence use the attributes. ('aq_base' should not be allowewd at all, as it strips away security context). There are probably thousands (or even tens of thousands) of templates and scripts in the wild which use these attributes. I don't think we can break them in a single release: we need to deprecate them first (with suitalbe logging output), and maybe even provide '__parent__'-aware workarounds / fallbacks in their implementations. This change is trivial to do and doesn't need to be done at first. It only needs to be done when you want to allow direct Zope 3 code in your application. As part of the branch all code in Zope 2 itself have been adjusted to use the aq_* methods. Good! Timeline: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? Hanno P.S. Thanks to philiKON for doing most of the work on this branch :) Many kudos to both of you. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIB4NT+gerLs4ltQ4RAvFlAKDLXkUC/ffrP4pGfNFC94Q815GcQgCfXqFU WqXqkO8p6JAZiOT4zpgg4wQ= =iWAn -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Hanno Schlichting wrote: Philipp von Weitershausen wrote: Hanno Schlichting wrote: Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. This sounds good. Here's another idea, though: In accordance with release early and often, how about scheduling the 2.12 release shortly after the 2.11 one? So the only new thing in 2.12 would be the philikon-aq branch (it would still ship with the same Zope 3 libraries as 2.11, etc.). I suspect we want to do something about the eggification story of Zope 2 for Zope 2.12 as well. Figuring out the approach and documenting it might take some additional time. I don't see that releasing another Zope 2.13 shortly after 2.12 makes a lot of sense. Why don't we get started on that, too, then? I think eggification of Zope 2 is relatively easy, and most of the necessary RD has already been done. In fact, a lot of the eggs exist already. I wonder if Philipp would be amenable to writing a proposal on this, and get Chris McDonough's input. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )