Re: [Zope3-dev] Zope 3.3.1 and 3.4
On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.3.1 and 3.4
Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk Christian -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Python version for Zope 3.4 ?
Christian Theune wrote: Morning, Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? Right now it's still Python 2.4, as Zope 3.4 is scheduled for next year, we should consider using Python 2.5 though. We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. ___ 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 3.3.1 and 3.4
Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. ___ 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 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. Can you repeat the specific rule for me? Christian -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ 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 3.3.1 and 3.4
Christian Theune wrote: Hi, I saw some updates in the wiki tonight and thought I'll catch up with some stuff too. As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of the door since yesterday, I've updated the roadmap. (Someone correct me if my information is out-dated) Current focus: Bug fixing Zope 3.3 -- Currently, we're aiming for a Zope 3.3 bugfix release (3.3.1) in November, which is managed by Martijn. Everybody is very encouraged to take a look at the collector and fix bugs instead of introducing new functionality. Please provide fixes and tests on the trunk and the 3.3 branch. ... *after* having it fixed on the 3.2 branch *first*. I'm the 3.2 bugfix manager and hope that we can soon have a 3.2.2 bugfix release as well. Next milestone: Zope 3.4 Due to the late release date for Zope 3.3 and the amount of open bugs, Zope 3.4 will be postponed one release cycle and will be released in May 2007. The largest project that I know of that aims for Zope 3.4 will be the eggification of Zope 3. I haven't seen a formal proposal for this yet, but AFAIK this is Jim's pet. Anybody else with larger features that are planned to go in for Zope 3.4? I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). ___ 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 3.3.1 and 3.4
Christian Theune wrote: Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. Can you repeat the specific rule for me? We'll repeat two stable branches, just like Zope 2. So, Zope 2 currently maintains 2.9 and 2.10. We maintain the Zope 3 counterparts, 3.2 and 3.3. ___ 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 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Christian -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ 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 3.3.1 and 3.4
Christian Theune wrote: Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Yup. There are some things in zope.app (e.g. workflow, externaleditor, zopetop, module, schemacontent) that aren't shipped with a Zope 3 install and don't seem to be maintained anymore. I suggest that if no-one steps up for them they will simply be deleted. There are also some things in zope.app that may be maintained but never shipped. These things don't really belong in zope.app, IMO (boston, homefolder, styleguide, css) and should probably be moved out. Discussions with their individual authors/maintainers will be necessary. Philipp ___ 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 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Yup. There are some things in zope.app (e.g. workflow, externaleditor, zopetop, module, schemacontent) that aren't shipped with a Zope 3 install and don't seem to be maintained anymore. I suggest that if no-one steps up for them they will simply be deleted. There are also some things in zope.app that may be maintained but never shipped. These things don't really belong in zope.app, IMO (boston, homefolder, styleguide, css) and should probably be moved out. Discussions with their individual authors/maintainers will be necessary. I agree on that. I'll put that on the prospective feature list so we don't forget about it. Christian -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Python version for Zope 3.4 ?
Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That would be loverly for both 3.4 and 2.11 :-D 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
Re: [Zope3-dev] Re: zcml questions
Jim Fulton wrote: That's pretty much what I suggested. The whole point of discriminators was conflict detection. That is why I suggested extending actions to support identifiers that could be used for overriding or disabling even for actions (or groups of actions) that don't otherwise conflict. This id scheme would leverage discriminators when present. Sounds cool, I only wish I could offer to help make it happen :-) 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: Python version for Zope 3.4 ?
Martijn Faassen wrote: Philipp von Weitershausen wrote: Christian Theune wrote: Morning, Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? Right now it's still Python 2.4, as Zope 3.4 is scheduled for next year, we should consider using Python 2.5 though. We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. I don't think we should commit to any official support for more than 1 Python version for a particular Zope. So either we certify Zope 2.11 for Python 2.5, or we stick to Python 2.4. Fine by me. My preference would be to get Zope 2.11 up to speed. If you're willing to do it :). The last time this was discussed with Jim, the idea was to try to use Zope 3's security proxy approach in Zope 2 for Python Script security - Jim and I had some ideas I need to dredge up from the back of my mind. That would of course be a great idea. Death to guarded_getattr! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.3.0 released!
2006/9/27, Philipp von Weitershausen [EMAIL PROTECTED]: On behalf of the Zope 3 development team I'm proud to announce the final Zope 3.3.0 release. There were no changes since the 3.3.0 release candidate. ... Thanks goes to everyone who contributed. There aren't AUTHORS file (zope 3 authors list) ? Stephane ___ 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 3.3.0 released!
KLEIN Stéphane wrote: 2006/9/27, Philipp von Weitershausen [EMAIL PROTECTED]: On behalf of the Zope 3 development team I'm proud to announce the final Zope 3.3.0 release. There were no changes since the 3.3.0 release candidate. ... Thanks goes to everyone who contributed. There aren't AUTHORS file (zope 3 authors list) ? See CHANGES.txt and CREDITS.txt ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Python version for Zope 3.4 ?
Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That's a good question. I fear it will take a fair bit of work to get to it and, frankly for me there are higher priorities. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: 7911 Blamelist: faassen,romanofski BUILD FAILED: failed test_2 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] buildbot failure in Zope3 trunk 2.4 Linux tlotze
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7911 Blamelist: faassen,romanofski BUILD FAILED: failed test_2 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] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7911 Blamelist: faassen,romanofski BUILD FAILED: failed test_2 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] Zope 3.3.1 and 3.4
Christian Theune wrote: Hi, I saw some updates in the wiki tonight and thought I'll catch up with some stuff too. As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of the door since yesterday, I've updated the roadmap. http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/RoadMap (Someone correct me if my information is out-dated) Current focus: Bug fixing Zope 3.3 -- Currently, we're aiming for a Zope 3.3 bugfix release (3.3.1) in November, which is managed by Martijn. Everybody is very encouraged to take a look at the collector and fix bugs instead of introducing new functionality. Please provide fixes and tests on the trunk and the 3.3 branch. Next milestone: Zope 3.4 Due to the late release date for Zope 3.3 and the amount of open bugs, Zope 3.4 will be postponed one release cycle and will be released in May 2007. Yup I think we should move the alpha and beta schedules up. IMO, we should schedule the first beta and thus the feature freeze for early April. The largest project that I know of that aims for Zope 3.4 will be the eggification of Zope 3. Yup. I fear that we if decide to support Python 2.5, that will be a bigger project. I haven't seen a formal proposal for this yet, Good point. but AFAIK this is Jim's pet. k Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Python version for Zope 3.4 ?
Chris Withers wrote: Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That would be loverly for both 3.4 and 2.11 :-D I think it will require a huge effort to get Zope 2 working with Python 2.5. Either: - We need to change Zope 2 to use Zope 3's security system, or - the RestrictedPython package will need to be reengineered to work with the substantially changed Python compiler and many new language features. I suspect that even Zope 3's security system will need a fair bit of work: - We need to rework or replace the small bit of RestrictedPython we use, and - If new Python type slots have been added, we'll need to reflect them in zope.proxy. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Heads up: Zope 3.2.2 on Saturday
Hello Philipp, Thursday, September 28, 2006, 3:48:34 PM, you wrote: By the way, it'd be cool if someone could do the Windows release. See http://dev.zope.org/Zope3/ZopeWindowsRelease for more info. I'm raising my hand. Doing it is OK, Updating the wiki page will take some time. -- Best regards, Adammailto:[EMAIL PROTECTED] -- Quote of the day: Every word is like an unnecessary stain on silence and nothingness.Everyone will experience the consequences of his own acts. If his acts are right, he'll get good consequences; if they're not, he'll suffer for it. (Harry Browne) ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.3.1 and 3.4
Jim Fulton wrote: As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of the door since yesterday, I've updated the roadmap. http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/RoadMap Jup. I think we should move the alpha and beta schedules up. IMO, we should schedule the first beta and thus the feature freeze for early April. Ah. Thanks for bringing that up. I thought about that already but forgot about that. I already thought the test times are too short. I'll move them up as suggested. The largest project that I know of that aims for Zope 3.4 will be the eggification of Zope 3. Yup. I fear that we if decide to support Python 2.5, that will be a bigger project. Ok. Something to do for Zope 3.5! -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ 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: Python version for Zope 3.4 ?
Martijn Faassen wrote: Philipp von Weitershausen wrote: Christian Theune wrote: Morning, Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? Right now it's still Python 2.4, as Zope 3.4 is scheduled for next year, we should consider using Python 2.5 though. We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. I don't think we should commit to any official support for more than 1 Python version for a particular Zope. So either we certify Zope 2.11 for Python 2.5, or we stick to Python 2.4. My preference would be to get Zope 2.11 up to speed. The last time this was discussed with Jim, the idea was to try to use Zope 3's security proxy approach in Zope 2 for Python Script security - Jim and I had some ideas I need to dredge up from the back of my mind. Jim, do you remember what was required? Not exactly, but it was a lot of work. See my other note about special challenges of 2.5 wrt security. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Heads up: Zope 3.2.2 on Saturday
Hello Philipp, BTW, correct me if I'm wrong, bugfixes go into: /repos/main/Zope3/branches/3.2 and /repos/main/Zope3/branches/3.3 Releases get built from: /repos/main/Zope3/tags/Zope-3.2.2 and /repos/main/Zope3/tags/Zope-3.3.1 -- Best regards, Groszer Adam -- Quote of the day: Feast, and your halls are crowded; fast, and the world goes by. - Ella Wheeler Wilcox ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Heads up: Zope 3.2.2 on Saturday
Adam Groszer wrote: Hello Philipp, BTW, correct me if I'm wrong, bugfixes go into: /repos/main/Zope3/branches/3.2 and /repos/main/Zope3/branches/3.3 ... and the trunk. Correct. Releases get built from: /repos/main/Zope3/tags/Zope-3.2.2 and /repos/main/Zope3/tags/Zope-3.3.1 Yup. ___ 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 tlotze
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7913 Blamelist: fdrake,romanofski,yusei BUILD FAILED: failed test_2 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] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7913 Blamelist: fdrake,romanofski,yusei BUILD FAILED: failed test_2 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] Python version for Zope 3.4 ?
Jim Fulton wrote: Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That's a good question. I fear it will take a fair bit of work to get to it and, frankly for me there are higher priorities. I think we'd be okay in not supporting Python 2.5 yet for this release. Python 2.5 has just been released, and the 9 months or so will give it time to gell out, Python extensions a bit of time to catch up with the newer version, and for us to do some experimenting. Linux distributions will likely still be supporting Python 2.4 (along with 2.5) at that stage as well. So unless a volunteer steps up to do lots of hard work between now and march next year, let's stick with Python 2.4. Otherwise let's plan it in for Zope 3.5 and Zope 2.12 Regards, Martijn ___ 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: Python version for Zope 3.4 ?
Philipp von Weitershausen wrote at 2006-9-28 11:22 +0200: ... The last time this was discussed with Jim, the idea was to try to use Zope 3's security proxy approach in Zope 2 for Python Script security - Jim and I had some ideas I need to dredge up from the back of my mind. I am quite fearful in this regard: Lots of existing code rely on the fact that trusted code can do anything without to worry about security. As security proxies restrict trusted code, too (though trusted code can remove the wrapper), we might get more security at the cost of massive backward incompatibility. -- Dieter ___ 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: Python version for Zope 3.4 ?
Dieter Maurer wrote: Philipp von Weitershausen wrote at 2006-9-28 11:22 +0200: ... The last time this was discussed with Jim, the idea was to try to use Zope 3's security proxy approach in Zope 2 for Python Script security - Jim and I had some ideas I need to dredge up from the back of my mind. I am quite fearful in this regard: Lots of existing code rely on the fact that trusted code can do anything without to worry about security. As security proxies restrict trusted code, too (though trusted code can remove the wrapper), we might get more security at the cost of massive backward incompatibility. As Zope 2 and Zope 3 merge in the long run, we'll have to worry about this at one point. The major question nowadays is: do we want/need to do it right now, or can we/should we procrastinate on this topic. Christian ___ 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: Python version for Zope 3.4 ?
On 9/28/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Christian Theune wrote: Morning, Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? Right now it's still Python 2.4, as Zope 3.4 is scheduled for next year, we should consider using Python 2.5 though. We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. Why isn't Python 2.5 even supported at present? Does Zope 3.3.0 flat-out break when run on 2.5? Or does Zope 3.3 + Python 2.5 work, but it hasn't been tested enough to say it's usable, but not required? -- Jeff Shell ___ 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: Python version for Zope 3.4 ?
Dieter Maurer wrote: Philipp von Weitershausen wrote at 2006-9-28 11:22 +0200: ... The last time this was discussed with Jim, the idea was to try to use Zope 3's security proxy approach in Zope 2 for Python Script security - Jim and I had some ideas I need to dredge up from the back of my mind. I am quite fearful in this regard: Lots of existing code rely on the fact that trusted code can do anything without to worry about security. As security proxies restrict trusted code, too (though trusted code can remove the wrapper), we might get more security at the cost of massive backward incompatibility. Yup. This is a real danger. My original plan was to allow either policy, making the Zope 3 policy optional. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: Python version for Zope 3.4 ?
Jeff Shell wrote: On 9/28/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Christian Theune wrote: Morning, Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? Right now it's still Python 2.4, as Zope 3.4 is scheduled for next year, we should consider using Python 2.5 though. We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. Why isn't Python 2.5 even supported at present? There are lots of test failures. Also, untrusted Python code doesn't work with 2.5 due to major changes in the compiler. (Zope 3 does almost no custom Python compiling, but it does do some.) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Fix the roadmap
Hi everybody. I noticed this in the roadmap. Planned schedule * Zope 3.4 alpha 1: mid-April, 2006 * Zope 3.4 beta 1: first week in May, 2006 * Zope 3.4 RC 1: mid-May, 2006 * Zope 3.4 final: last week of May, 2006 Shouldn't those be 2007? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: Re: [Zope3-dev] Python version for Zope 3.4 ?
On 9/28/06, Martijn Faassen [EMAIL PROTECTED] wrote: Jim Fulton wrote: Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That's a good question. I fear it will take a fair bit of work to get to it and, frankly for me there are higher priorities. I think we'd be okay in not supporting Python 2.5 yet for this release. Python 2.5 has just been released, and the 9 months or so will give it time to gell out, Python extensions a bit of time to catch up with the newer version, and for us to do some experimenting. Linux distributions will likely still be supporting Python 2.4 (along with 2.5) at that stage as well. Are you talking not-supporting Python 2.5 at all? Or just not wanting to require it? If Zope 3 can't at least run on Python 2.5 within three months of Python 2.5's release, I don't think that looks good for us. I would hope that by being more Pythonic and free from the old ExtensionClass magic - especially in Zope 3 - that Zope could keep better pace with Python. But nine months? A year? Can I expect the developers of toolkits we use, in some cases more heavily than Zope itself, like SQLAlchemy to hold off on requiring Python 2.5 for that long? So unless a volunteer steps up to do lots of hard work between now and march next year, let's stick with Python 2.4. Otherwise let's plan it in for Zope 3.5 and Zope 2.12 I really really really hope it doesn't take that long to be able to at least run on Python 2.5: even if it has to be with some caveats or mild warnings. If security and restricted python / security proxies are the main issue, what about if one is running Zope sites with absolutely ZERO through the web code - no page templates, nothing - can't there be a lighter weight security implementation that wouldn't take half a year of lots of hard work? -- Jeff Shell ___ 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 branches 3.3 2.4 Linux remy
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Linux remy. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7921 Blamelist: faassen,fdrake,jim,romanofski,wosc,yuppie,yusei BUILD FAILED: failed test 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: Re: Use launchpad ! (was Re: [Zope3-dev] the maintenance of change logs)
On 9/25/06, Martijn Faassen [EMAIL PROTECTED] wrote: Baiju M wrote: On 9/22/06, Jim Fulton [EMAIL PROTECTED] wrote: snip Finally, I'm experimenting with using launchpad for bugs: https://launchpad.net/products/zc.buildout/+bugs and feature requests: https://features.launchpad.net/products/zc.buildout/ So far this is working OK. I haven't really stressed it. Launchpad makes this very easy to set up and I don't think they are allergic to having us create lots of projects. Let's move Zope3 issue collector to launchpad? (Once this discussion came to ZF list, I think there were more +1) Before we move any issue collectors to launchpad, we need a bit more experience with the launchpad issue tracker and its capabilities. I'm also wonder whether launchpad has good issue export facilities in case we want to move to another system. With Tres, I think we should also explore options like Trac. I personally think Trac has attractive features in the way it integrates the development process into things like an issue tracker. I love Trac. I've never installed it or used it to manage any projects on my own, but I find that I stay on top of open source projects more if they're using Trac. On a small aesthetics side, I find Launchpad's side bars incredibly distracting, and I don't like looking at the page because it feels like there are too many things vying for my attention and I have a hard time really reading the text in front of me. The content gets squished. And then I find myself looking at all of these links and buttons around the page trying to figure out what has the information I'm interested in. The sidebar on Zope.org bothers me in the same way when I try to read the Zope 3 wiki - but Zope.org feels nowhere near as noisy as Launchpad. I'm sure their tools are great, and the hosting service is a good feature. But my temper is short these days. My attention span is not: if I can find and read a page that's not full of distractions, I'll stay and read it and learn. But when there are boxes on all sides chock full of colors and links, reading is much harder. A nice simple example is this nice page in SQLAlchemy's Trac wiki (a page I read over and over as I migrated code to 0.2): http://www.sqlalchemy.org/trac/wiki/02Migration It's very nice. I can read that page, print it, save it to a local permanent archive, etc. There is something about Trac's feature set, implementation, and in how it's installed (in most cases) that make it very nice for a cantankerous, stressed out, often overburdened worker like me to stay on top of and even want to get involved (even on some small level) with a project - and that I can do this in small amounts of time. The Zope 3 wiki, collector, and even subversion browser, all feel like they require more of a full time job to stay involved. And if not a full time job, then at least some seriously set-aside time. It's very hard to get answers to what's gone on recently?, what are all of the bugs, and let me see and sort them quickly on some different criteria, and let me then see how they were fixed, and then let me quickly find some minor annoyance issues that I might be able to fix. With a Trac setup like SQLAlchemy is using, I feel like I can do this at home in the morning during my browse-and-drink-coffee-time. With the current Zope tools (and my limited experience with Launchpad's tools), it does not feel casual at all to keep up with everything going on. And that makes it hard to stay enthusiastic and energized about a project. Compare: - http://dev.zope.org/Zope3/RoadMap - http://www.sqlalchemy.org/trac/milestone/0.3.0?by=severity I wish there had been something like that Trac milestone page for Zope 3.3. Of course, it doesn't show everything going on. But it would have made it much easier to find out what may have been slowing the release down so much, and then easier to want to get involved and make it happen sooner. The lack of distracting side columns, the integration of the Wiki, the Roadmaps/Milestones, the Subversion integration (being able to refer to tickets, wiki pages, etc in commit log messages and having the links generated in the web. [ticket:309], etc), the custom issue tracker reports: it's a very nice system to use, even casually. The Timeline is like a Wiki's Recent Changes on crack. Except the crack is filled with helpful vitamins: recent wiki changes, recent checkins, recent issue tracker activity (bugs submitted, opened, closed). It just feels so much more alive. -- Jeff Shell ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] test for security in unit tests?
Hi Folks, I find that testing for security is hard, since the default user in the doctests seems to have unrestricted access to all methods and attributes. Is there a unit-test friendly way of faking a user with a more restricted role, so that I can reproduce security errors in unit tests? Thanks, Roy Mathew ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Python version for Zope 3.4 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Shell wrote: On 9/28/06, Martijn Faassen [EMAIL PROTECTED] wrote: Jim Fulton wrote: Baiju M wrote: Hi, What is the target Python version for Zope 3.4, is it Python 2.5? That's a good question. I fear it will take a fair bit of work to get to it and, frankly for me there are higher priorities. I think we'd be okay in not supporting Python 2.5 yet for this release. Python 2.5 has just been released, and the 9 months or so will give it time to gell out, Python extensions a bit of time to catch up with the newer version, and for us to do some experimenting. Linux distributions will likely still be supporting Python 2.4 (along with 2.5) at that stage as well. Are you talking not-supporting Python 2.5 at all? Or just not wanting to require it? The proposal is not to support it at all, unless somebody takes one for the team and works out all the nasty breakage which 2.5 induces on Zope. If Zope 3 can't at least run on Python 2.5 within three months of Python 2.5's release, I don't think that looks good for us. I would hope that by being more Pythonic and free from the old ExtensionClass magic - especially in Zope 3 - that Zope could keep better pace with Python. But nine months? A year? Can I expect the developers of toolkits we use, in some cases more heavily than Zope itself, like SQLAlchemy to hold off on requiring Python 2.5 for that long? The change from 2.4 to 2.5 is *massively* disruptive for a framework like Zope: much more so than any change since 2.2, I think (maybe even 2.0/2.1). The hardest bit is the change to the way the compiler works: RestrictedPython is completely incompatible with the new AST-based strategy. So unless a volunteer steps up to do lots of hard work between now and march next year, let's stick with Python 2.4. Otherwise let's plan it in for Zope 3.5 and Zope 2.12 I really really really hope it doesn't take that long to be able to at least run on Python 2.5: even if it has to be with some caveats or mild warnings. If security and restricted python / security proxies are the main issue, what about if one is running Zope sites with absolutely ZERO through the web code - no page templates, nothing - can't there be a lighter weight security implementation that wouldn't take half a year of lots of hard work? Even if you have no templates defined TTW, Zope3's security machiner still needs some support from RestrictedPython for handling filesystem-based templates. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFHJr3+gerLs4ltQ4RAnmFAKCuFkvWIAVn60mLP8AIik9LcttATgCcDrIL KQjhDIoPaj9N9pL1JHGIZU4= =D1Zt -END PGP SIGNATURE- ___ 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: Python version for Zope 3.4 ?
--On 28. September 2006 16:17:54 -0400 Jim Fulton [EMAIL PROTECTED] wrote: We should definitely try to *support* Python 2.5, but we can't require it till Zope 2 has been certified for it. Why isn't Python 2.5 even supported at present? There are lots of test failures. Also, untrusted Python code doesn't work with 2.5 due to major changes in the compiler. (Zope 3 does almost no custom Python compiling, but it does do some.) Also Zope 2.10 dies under Python 2.5 with some famous crashs. -aj pgpbvMiP3G4pc.pgp Description: PGP signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Fix the roadmap
Douglas Douglas wrote: Hi everybody. I noticed this in the roadmap. Planned schedule * Zope 3.4 alpha 1: mid-April, 2006 * Zope 3.4 beta 1: first week in May, 2006 * Zope 3.4 RC 1: mid-May, 2006 * Zope 3.4 final: last week of May, 2006 Shouldn't those be 2007? Sure. I'm living off-calendar. =) I'm putting in the changes to the test period as well, as nobody objected since yesterday. Thanks for the hint. Christian -- gocept gmbh co. kg - forsterstraße 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 signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
