[Zope-Checkins] SVN: Zope/branches/2.12/ Prepare Zope2 2.12.9.
Log message for revision 114668: Prepare Zope2 2.12.9. Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/setup.py U Zope/branches/2.12/versions.cfg -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-07-13 07:38:19 UTC (rev 114667) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-07-13 08:31:23 UTC (rev 114668) @@ -5,7 +5,7 @@ Change information for previous versions of Zope can be found at http://docs.zope.org/zope2/releases/. -2.12.9 (unreleased) +2.12.9 (2010-07-13) --- Bugs Fixed @@ -24,8 +24,8 @@ - Factored out the `Products.ZSQLMethods` into its own distribution. The distribution also includes the `Shared.DC.ZRDB` code. The code is no longer included in Zope 2.13. If you rely on it, please specify a dependency on - the new `Products.ZSQLMethod` distribution. This will only work for code that - requires at least Zope 2.12.9. + the new `Products.ZSQLMethods` distribution. This will only work for code + that requires at least Zope 2.12.9. - Made both `Shared` and `Shared.DC` namespace packages. Modified: Zope/branches/2.12/setup.py === --- Zope/branches/2.12/setup.py 2010-07-13 07:38:19 UTC (rev 114667) +++ Zope/branches/2.12/setup.py 2010-07-13 08:31:23 UTC (rev 114668) @@ -16,7 +16,7 @@ from setuptools import setup, find_packages, Extension setup(name='Zope2', -version='2.12.9dev', +version='2.12.9', url='http://www.zope.org', license='ZPL 2.1', description='Zope2 application server / web framework', Modified: Zope/branches/2.12/versions.cfg === --- Zope/branches/2.12/versions.cfg 2010-07-13 07:38:19 UTC (rev 114667) +++ Zope/branches/2.12/versions.cfg 2010-07-13 08:31:23 UTC (rev 114668) @@ -2,7 +2,7 @@ versions = versions [versions] -Zope2 = +Zope2 = 2.12.9 Acquisition = 2.13.3 buildout.dumppickedversions = 0.4 ClientForm = 0.2.10 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.12.9/ Tagged Zope2 2.12.9.
Log message for revision 114669: Tagged Zope2 2.12.9. Changed: A Zope/tags/2.12.9/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/ Bump version
Log message for revision 114670: Bump version Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/setup.py U Zope/branches/2.12/versions.cfg -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-07-13 08:31:36 UTC (rev 114669) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-07-13 08:32:46 UTC (rev 114670) @@ -5,6 +5,13 @@ Change information for previous versions of Zope can be found at http://docs.zope.org/zope2/releases/. +2.12.10 (unreleased) + + +Bugs Fixed +++ + + 2.12.9 (2010-07-13) --- Modified: Zope/branches/2.12/setup.py === --- Zope/branches/2.12/setup.py 2010-07-13 08:31:36 UTC (rev 114669) +++ Zope/branches/2.12/setup.py 2010-07-13 08:32:46 UTC (rev 114670) @@ -16,7 +16,7 @@ from setuptools import setup, find_packages, Extension setup(name='Zope2', -version='2.12.9', +version='2.12.10dev', url='http://www.zope.org', license='ZPL 2.1', description='Zope2 application server / web framework', Modified: Zope/branches/2.12/versions.cfg === --- Zope/branches/2.12/versions.cfg 2010-07-13 08:31:36 UTC (rev 114669) +++ Zope/branches/2.12/versions.cfg 2010-07-13 08:32:46 UTC (rev 114670) @@ -2,7 +2,7 @@ versions = versions [versions] -Zope2 = 2.12.9 +Zope2 = Acquisition = 2.13.3 buildout.dumppickedversions = 0.4 ClientForm = 0.2.10 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.13.0a2/ Tagged Zope2 2.13.0a2.
Log message for revision 114673: Tagged Zope2 2.13.0a2. Changed: A Zope/tags/2.13.0a2/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Bump version
Log message for revision 114674: Bump version Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/setup.py U Zope/trunk/versions.cfg -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2010-07-13 08:51:38 UTC (rev 114673) +++ Zope/trunk/doc/CHANGES.rst 2010-07-13 08:52:30 UTC (rev 114674) @@ -5,6 +5,21 @@ Change information for previous versions of Zope can be found at http://docs.zope.org/zope2/releases/. +2.13.0a3 (unreleased) +- + +Bugs Fixed +++ + + +Restructuring ++ + + +Features Added +++ + + 2.13.0a2 (2010-07-13) - Modified: Zope/trunk/setup.py === --- Zope/trunk/setup.py 2010-07-13 08:51:38 UTC (rev 114673) +++ Zope/trunk/setup.py 2010-07-13 08:52:30 UTC (rev 114674) @@ -17,7 +17,7 @@ setup(name='Zope2', -version='2.13.0a2', +version='2.13.0a3.dev', url='http://zope2.zope.org', license='ZPL 2.1', description='Zope2 application server / web framework', Modified: Zope/trunk/versions.cfg === --- Zope/trunk/versions.cfg 2010-07-13 08:51:38 UTC (rev 114673) +++ Zope/trunk/versions.cfg 2010-07-13 08:52:30 UTC (rev 114674) @@ -4,7 +4,7 @@ [versions] # Zope2-specific -Zope2 = 2.13.0a2 +Zope2 = AccessControl = 2.13.1 Acquisition = 2.13.3 DateTime = 2.12.4 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/doc/CHANGES.rst Correct changelog
Log message for revision 114692: Correct changelog Changed: U Zope/trunk/doc/CHANGES.rst -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2010-07-13 10:16:12 UTC (rev 114691) +++ Zope/trunk/doc/CHANGES.rst 2010-07-13 10:18:48 UTC (rev 114692) @@ -30,9 +30,8 @@ - LP #143531: Fix broken object so they give access to their state. -- LP #578326: Issue a warning if someone specifies a non-public permission - attribute in the browser:view directive. This attribute has never been - supported in Zope 2. +- LP #578326: Add support for non-public permission attributes in the + browser:view directive. Restructuring + ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Update to ZODB3 = 3.10.0b2
Log message for revision 114719: Update to ZODB3 = 3.10.0b2 Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/versions.cfg -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2010-07-13 16:36:16 UTC (rev 114718) +++ Zope/trunk/doc/CHANGES.rst 2010-07-13 16:45:38 UTC (rev 114719) @@ -22,7 +22,10 @@ Features Added ++ +- Updated packages: + - ZODB3 = 3.10.0b2 + 2.13.0a2 (2010-07-13) - Modified: Zope/trunk/versions.cfg === --- Zope/trunk/versions.cfg 2010-07-13 16:36:16 UTC (rev 114718) +++ Zope/trunk/versions.cfg 2010-07-13 16:45:38 UTC (rev 114719) @@ -30,7 +30,7 @@ ZopeUndo = 2.12.0 # ZTK KGS overrides -ZODB3 = 3.10.0b1 +ZODB3 = 3.10.0b2 # Zope2 dependencies repoze.retry = 0.9.4 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] New releases of Zope2 (incl. a potential security fix)
Hi. I released Zope 2.12.9 and Zope 2.13.0a2 today. Both contain a fix for the missing browser:view permission support (https://bugs.launchpad.net/zope2/+bug/578326). As this might affect security of your applications, you are advised to upgrade. Zope 2 itself is not vulnerable. Thanks goes to Martin Aspeli for implementing this support on short notice. In other news Zope 2.13.0a2 now officially supports Python 2.7. Special thanks to David Glick for performing the security audit of RestrictedPython. You can read more about the changes at http://docs.zope.org/zope2/releases/2.13/CHANGES.html. All the best, Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 53 OK, 16 Failed, 3 Unknown
Summary of messages to the zope-tests list. Period Mon Jul 12 12:00:00 2010 UTC to Tue Jul 13 12:00:00 2010 UTC. There were 72 messages: 6 from Zope Tests, 3 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 17 from buildbot at winbot.zope.org, 13 from ccomb at free.fr, 1 from ct at gocept.com, 28 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED: Repository policy check found errors in 414 projects From: ct at gocept.com Date: Mon Jul 12 21:14:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016549.html Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon Jul 12 22:04:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016557.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon Jul 12 22:05:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016558.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon Jul 12 22:05:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016559.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Mon Jul 12 22:58:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016566.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Mon Jul 12 23:09:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016567.html Subject: FAILED : winbot / ztk_10 py_270_win32 From: buildbot at winbot.zope.org Date: Mon Jul 12 23:46:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016572.html Subject: FAILED : winbot / ztk_10 py_270_win64 From: buildbot at winbot.zope.org Date: Mon Jul 12 23:53:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016573.html Subject: FAILED : ZTK 1.0dev / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Tue Jul 13 00:16:38 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016575.html Subject: FAILED : winbot / ZODB_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Jul 13 00:56:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016579.html Subject: FAILED : winbot / ZODB_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Jul 13 01:51:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016581.html Subject: FAILED : ZTK 1.0 / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Tue Jul 13 01:52:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016583.html Subject: FAILED : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Jul 13 02:46:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016586.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Jul 13 03:48:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016588.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Jul 13 04:47:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016591.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 13 07:11:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016598.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 13 03:00:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016587.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.5-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 13 03:55:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016589.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.4-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 13 04:07:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016590.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Jul 12 08:06:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016539.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Jul 12 08:08:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016540.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Jul 12 08:13:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016541.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Jul 12 14:55:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016542.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com
[Zope-dev] Can ZTK 1.0 support Python 2.7?
Hi. We have Python 2.7 final now and some work has begun on making ZTK packages compatible with it. Currently we still see various test failures in the zopeapp set though and nobody who steps up to fix them. Apart from that, we have made a promise to support Python 2.4 up to 2.6 for the ZTK 1.0 release. The ZODB 3.10 releases do no longer support Python 2.4 but require 2.5. The ZODB 3.9.x releases are in maintenance mode for a while and currently don't support Python 2.7. I doubt that we can get official 2.7 support for the 3.9.x release line. Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. What do others think about this? Hanno P.S. We talked about a rough timeline for a ZTK 1.0 release in the release team. We are aiming to get a beta out in early August (once we are all back from vacation). Test failures on any of the supported platforms are blocking such a release. This includes any failures we get on Windows. Hopefully more community members will step up and help fix those. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On Tuesday, July 13, 2010, Hanno Schlichting wrote: What do others think about this? Based on what you wrote, I think this is the right solution. Python 2.4 is clearly important to the Zope 2 / Plone world. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New releases of Zope2 (incl. a potential security fix)
On Tuesday, July 13, 2010, Hanno Schlichting wrote: In other news Zope 2.13.0a2 now officially supports Python 2.7. How can Zope 2.13 support Python 2.7, when the ZTK 1.0 does not? Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On Tue, Jul 13, 2010 at 3:07 PM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Tuesday, July 13, 2010, Hanno Schlichting wrote: What do others think about this? Based on what you wrote, I think this is the right solution. Python 2.4 is clearly important to the Zope 2 / Plone world. Actually both Zope2 and Plone 4 (as a potential user of the ZTK) are requiring Python 2.6 and don't even support Python 2.5 anymore. It's BlueBream and direct ZTK consumers that asked for the Python 2.4 support ;-) Anyways we decided to keep Python 2.4 for a ZTK release and codified that at http://docs.zope.org/zopetoolkit/process/python-versions.html Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
Am 13.07.2010, 14:12 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu: What do others think about this? Hanno, what's the time frame for ZTK 1.0? From your previous mail there were three packages with test failures on 2.7. But I thought these were fixed? I fixed all of those and released new versions. bin/test-ztk should now pass under Python 2.7. Have I missed a mail with more failures? I would have thought getting those tests to pass for a release is a reasonable aim. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New releases of Zope2 (incl. a potential security fix)
On Tue, Jul 13, 2010 at 3:08 PM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Tuesday, July 13, 2010, Hanno Schlichting wrote: In other news Zope 2.13.0a2 now officially supports Python 2.7. How can Zope 2.13 support Python 2.7, when the ZTK 1.0 does not? Zope 2.13 only uses the ZTK core part and overrides the ZODB3 requirement to use a 3.10 release. All tests on Python 2.7 pass for all the zope.* packages. It's only the zopeapp set and the ZODB which aren't compatible. So from a Zope2 perspective we can support Python 2.7 in addition to 2.6 rather easily. Since everything works, it doesn't make a lot of sense to hold off official 2.7 support. The ZTK has more code and other Python versions to support, so it's in a different position. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On Tue, Jul 13, 2010 at 3:23 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: what's the time frame for ZTK 1.0? I put that info into the post scriptum of my mail. Have I missed a mail with more failures? I would have thought getting those tests to pass for a release is a reasonable aim. You have. It's only bin/test-ztk that passes. bin/test-zopeapp still has a number of failures. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: On Tue, Jul 13, 2010 at 3:23 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: what's the time frame for ZTK 1.0? I put that info into the post scriptum of my mail. Have I missed a mail with more failures? I would have thought getting those tests to pass for a release is a reasonable aim. You have. It's only bin/test-ztk that passes. bin/test-zopeapp still has a number of failures. There is also the zope.testing failure where a doctest tries to drive the pdb module: 2.7 added a new intermediate (private) method to the call stack in unittest's 'assertEqual', which causes that test to fail. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw8cboACgkQ+gerLs4ltQ4SHACfUniSb5VOU8A0eWww1uyr+Nav QUsAoMt8Dbz+DT4ZTcv1SA1gB6Oep+Us =JyFb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
Hi,
The latest Zope 2.12.9 release broke the last release of Products.ZMySQLDA.
To demonstrate, bootstrap and run the attached buildout, then run:
$ bin/py -c import Shared.DC.ZRDB, Products.ZMySQLDA
You'll get the following traceback:
Traceback (most recent call last):
File bin/py, line 107, in module
exec _val
File string, line 1, in module
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/__init__.py,
line 90, in module
import DA
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/DA.py,
line 243, in module
os.path.join('Shared','DC','ZRDB','www','DBAdapterFolder_icon.gif'))}
File
/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/App/ImageFile.py,
line 77, in __init__
stat_info = os.stat(path)
OSError: [Errno 2] No such file or directory:
'/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/Shared/DC/ZRDB/www/DBAdapterFolder_icon.gif'
Edit buildout.cfg and switch the extends directive to the commented
out 2.12.8 tag and see that the above command shows no error, only a
deprecation warning that is unrelated to the breakage above.
Internal buildbots that tracked the 2.12 branch notified me of this
problem, but in between catching up with all the traffic for the
mailing lists and the Zope commit, and a day job, I didn't have enough
time to track down the issue before the 2.12.9 release was made: there
was less than 4 days between spinning off Products.ZSQLMethods and the
new 2.12 release.
The most trivial fix seems fairly obvious: ZMySQLDA should carry its
own icon, but in any case, Zope 2.12 should not break compatibility in
the middle of a stable series. I strongly suspect other Zope2 DB
adapters to suffer from the same problem.
I'm not sure what the proper fix should be. App.ImageFile.ImageFile
could grow support for icons outside of software_home, or perhaps the
spinning-off of Shared.DC.ZRDB should be delayed to the 2.13 series
only, but in any case the 2.12 branch should be a safe upgrade for
third party code as much as reasonably possible.
suggestions?
Cheers,
Leo
buildout.cfg
Description: application/httpd-cgi
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
Hi.
On Tue, Jul 13, 2010 at 5:13 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
The latest Zope 2.12.9 release broke the last release of Products.ZMySQLDA.
You are not by any chance interested in taking over maintenance of
ZSQLMethods, are you?
You'll get the following traceback:
Traceback (most recent call last):
File bin/py, line 107, in module
exec _val
File string, line 1, in module
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/__init__.py,
line 90, in module
import DA
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/DA.py,
line 243, in module
os.path.join('Shared','DC','ZRDB','www','DBAdapterFolder_icon.gif'))}
File
/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/App/ImageFile.py,
line 77, in __init__
stat_info = os.stat(path)
OSError: [Errno 2] No such file or directory:
'/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/Shared/DC/ZRDB/www/DBAdapterFolder_icon.gif'
The most trivial fix seems fairly obvious: ZMySQLDA should carry its
own icon, but in any case, Zope 2.12 should not break compatibility in
the middle of a stable series. I strongly suspect other Zope2 DB
adapters to suffer from the same problem.
We documented it pretty clearly in the Zope 2.12.0 release notes, that
you can no longer rely on software home or zope home. See for example
http://docs.zope.org/zope2/releases/2.12/WHATSNEW.html#fully-eggified
The code should have long been changed to import Shared.DC.ZRDB and
then os.path.join(ZRDB.__file__, 'www', 'DBAdapterFolder_icon.gif') or
better yet use its own icon. Both of these would have worked with all
2.12.x releases.
I'm not sure what the proper fix should be. App.ImageFile.ImageFile
could grow support for icons outside of software_home, or perhaps the
spinning-off of Shared.DC.ZRDB should be delayed to the 2.13 series
only, but in any case the 2.12 branch should be a safe upgrade for
third party code as much as reasonably possible.
We don't make guarantees on internals. Zope 2 always had a policy of
allowing minor changes and new features to occur in the stable release
series. It's not just pure bugfix releases.
I think in this case the code in Products.ZMySQLDA should be changed
to be compatible with Zope 2.12.
Hanno
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On 07/13/2010 02:12 PM, Hanno Schlichting wrote: Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. +1 For Zope standards we'd still be very fast with supporting Python 2.7 if we do this (assuming 1.1 will be out before, say, 2012 :). Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On Tue, Jul 13, 2010 at 2:12 PM, Hanno Schlichting ha...@hannosch.eu wrote: Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. We discussed this in todays zope-dev IRC meeting. There was general support for this approach. The 1.1 release should follow the 1.0 release rather soon in this case. I'll bring it up in the release team. Thanks all, Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
Am 13.07.2010, 17:44 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu: You are not by any chance interested in taking over maintenance of ZSQLMethods, are you? As I've still got some stuff running on ZSQL and have previously championed it I'll also wave a hand, although I'm not that familiar with the internals so am not in a position to maintain it on my own. I'd like to see a scaled back version of ZSQL survive as I think there is a compelling TTW use case but I would drop the most of the dedicated dtml-sql methods as not suitable for this kind of use. Essentially I'd like to see templates generating statements with positional placeholders to be passed to .execute(stmt, paras) calls. I'm sure I remember seeing something like SmartTemplate a few years ago which looked suitable for this. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
Hi
On Tue, Jul 13, 2010 at 12:44, Hanno Schlichting ha...@hannosch.eu wrote:
[...]
You'll get the following traceback:
Traceback (most recent call last):
File bin/py, line 107, in module
exec _val
File string, line 1, in module
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/__init__.py,
line 90, in module
import DA
File
/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/DA.py,
line 243, in module
os.path.join('Shared','DC','ZRDB','www','DBAdapterFolder_icon.gif'))}
File
/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/App/ImageFile.py,
line 77, in __init__
stat_info = os.stat(path)
OSError: [Errno 2] No such file or directory:
'/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/Shared/DC/ZRDB/www/DBAdapterFolder_icon.gif'
The most trivial fix seems fairly obvious: ZMySQLDA should carry its
own icon, but in any case, Zope 2.12 should not break compatibility in
the middle of a stable series. I strongly suspect other Zope2 DB
adapters to suffer from the same problem.
We documented it pretty clearly in the Zope 2.12.0 release notes, that
you can no longer rely on software home or zope home. See for example
http://docs.zope.org/zope2/releases/2.12/WHATSNEW.html#fully-eggified
The code should have long been changed to import Shared.DC.ZRDB and
then os.path.join(ZRDB.__file__, 'www', 'DBAdapterFolder_icon.gif') or
better yet use its own icon. Both of these would have worked with all
2.12.x releases.
the call that failed is this:
ImageFile(os.path.join('Shared','DC','ZRDB','www','DBAdapterFolder_icon.gif'))
There is no explicit mention of software home anywhere, and there
was no warning that this API was being used in a deprecated way.
In fact, the use of software home happens inside ImageFile itself:
def __init__(self, path, _prefix=None):
import Globals # for data
if _prefix is None:
_prefix=getattr(getConfiguration(), 'softwarehome', PREFIX)
elif type(_prefix) is not type(''):
_prefix=package_home(_prefix)
Of course I and most people on this list can read the ImageFile() call
above and probably get a good hunch that sofware_home is being assumed
somewhere, but a cursory reading of the call could also imply that a
data file is simply being read relative to the Zope2 package location,
and that this is supported behaviour of the ImageFile class.
I'm not sure what the proper fix should be. App.ImageFile.ImageFile
could grow support for icons outside of software_home, or perhaps the
spinning-off of Shared.DC.ZRDB should be delayed to the 2.13 series
only, but in any case the 2.12 branch should be a safe upgrade for
third party code as much as reasonably possible.
We don't make guarantees on internals. Zope 2 always had a policy of
allowing minor changes and new features to occur in the stable release
series. It's not just pure bugfix releases.
And I'm not disagreeing with the policy, but it can be argued that
depending on the location of *data* files inside the Zope2 package is
not necessarily relying on guarantees on internals.
I think in this case the code in Products.ZMySQLDA should be changed
to be compatible with Zope 2.12.
Obviously. Still, App.ImageFile.ImageFile (and any other Zope2 APIs
that do rely on software_home) should give a clear warning when
software_home is assumed, since it is the one assuming it. The
exception raised by the ImageFile call now gives no clue on what
actually went wrong and what a developer should do about it.
Cheers,
Leo
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
On Tue, Jul 13, 2010 at 7:05 PM, Leonardo Rochael Almeida leoroch...@gmail.com wrote: And I'm not disagreeing with the policy, but it can be argued that depending on the location of *data* files inside the Zope2 package is not necessarily relying on guarantees on internals. I'd call anything that relies on a specific file system layout to be internals. We only make guarantees on the semantics of the Python import system, not how packages and modules are stitched together in distributions and end up on the file system. Obviously. Still, App.ImageFile.ImageFile (and any other Zope2 APIs that do rely on software_home) should give a clear warning when software_home is assumed, since it is the one assuming it. The exception raised by the ImageFile call now gives no clue on what actually went wrong and what a developer should do about it. I agree with that. I thought the call to software home was being made inside ZMySQLDA and not in Zope 2 code. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On 2010-07-13 14:12:01 +0200, Hanno Schlichting said: Hi. We have Python 2.7 final now and some work has begun on making ZTK packages compatible with it. Currently we still see various test failures in the zopeapp set though and nobody who steps up to fix them. Apart from that, we have made a promise to support Python 2.4 up to 2.6 for the ZTK 1.0 release. The ZODB 3.10 releases do no longer support Python 2.4 but require 2.5. The ZODB 3.9.x releases are in maintenance mode for a while and currently don't support Python 2.7. I doubt that we can get official 2.7 support for the 3.9.x release line. Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. Yes, ZTK 1.0 should become stable/released soon. Adding a new Python version or removing one, doesn't help. But I really want to see Python 2.7 support rather soon. So how do we actually proceed there? Even after ZTK 1.0 is out, how is the transition made to 1.1? I suppose there could be a 1.0.1 at the same time as a 1.1.0. Regards, -- Christian Zagrodnick · c...@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 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Zagrodnick wrote: On 2010-07-13 14:12:01 +0200, Hanno Schlichting said: Hi. We have Python 2.7 final now and some work has begun on making ZTK packages compatible with it. Currently we still see various test failures in the zopeapp set though and nobody who steps up to fix them. Apart from that, we have made a promise to support Python 2.4 up to 2.6 for the ZTK 1.0 release. The ZODB 3.10 releases do no longer support Python 2.4 but require 2.5. The ZODB 3.9.x releases are in maintenance mode for a while and currently don't support Python 2.7. I doubt that we can get official 2.7 support for the 3.9.x release line. Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. Yes, ZTK 1.0 should become stable/released soon. Adding a new Python version or removing one, doesn't help. But I really want to see Python 2.7 support rather soon. So how do we actually proceed there? Even after ZTK 1.0 is out, how is the transition made to 1.1? I suppose there could be a 1.0.1 at the same time as a 1.1.0. As soon as we get to 1.0b1, the release team will make a 'branches/1.0' branch for stabilization, and the trunk can then be updated to drop 2.4 support and add 2.7 support. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw8snEACgkQ+gerLs4ltQ60igCfdL4gBCN3vGoxRgsD4bKOoyhX PqMAn28VTzBhMAt5xGQSXWbIBoyhIXKB =y36w -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On 2010-07-13 20:37:42 +0200, Tres Seaver said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Zagrodnick wrote: On 2010-07-13 14:12:01 +0200, Hanno Schlichting said: Hi. We have Python 2.7 final now and some work has begun on making ZTK packages compatible with it. Currently we still see various test failures in the zopeapp set though and nobody who steps up to fix them. Apart from that, we have made a promise to support Python 2.4 up to 2.6 for the ZTK 1.0 release. The ZODB 3.10 releases do no longer support Python 2.4 but require 2.5. The ZODB 3.9.x releases are in maintenance mode for a while and currently don't support Python 2.7. I doubt that we can get official 2.7 support for the 3.9.x release line. Given all of these, I'm leaning towards not supporting Python 2.7 for a ZTK 1.0 release. A 1.1 can drop Python 2.4 support and we can try to support 2.7 in addition. Yes, ZTK 1.0 should become stable/released soon. Adding a new Python version or removing one, doesn't help. But I really want to see Python 2.7 support rather soon. So how do we actually proceed there? Even after ZTK 1.0 is out, how is the transition made to 1.1? I suppose there could be a 1.0.1 at the same time as a 1.1.0. As soon as we get to 1.0b1, the release team will make a 'branches/1.0' branch for stabilization, and the trunk can then be updated to drop 2.4 support and add 2.7 support. Actually I was thinking about the individual packages. I assume dropping Python 2.4 should bump the respective package version at least from 1.x.y to 1.x+1.0, right? -- Christian Zagrodnick · c...@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 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
Am 13.07.2010, 20:48 Uhr, schrieb Christian Zagrodnick c...@gocept.com: Actually I was thinking about the individual packages. I assume dropping Python 2.4 should bump the respective package version at least from 1.x.y to 1.x+1.0, right? ZTK 1.1 will officially not support Python 2.6 but it won't seek to actively break 2.4 and 2.5. It sounds like you are suggesting what to do about packages that definitely don't work with 2.6. While I would have thought a syntax change shouldn't mean a major version, breaking compatibility obviously warrants some thought. But then I wouldn't expect a release just based on new syntax. Have you got a specific example in mind? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
On Tue, Jul 13, 2010 at 10:01:35AM -0400, Tres Seaver wrote: Hanno Schlichting wrote: On Tue, Jul 13, 2010 at 3:23 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: what's the time frame for ZTK 1.0? I put that info into the post scriptum of my mail. Have I missed a mail with more failures? I would have thought getting those tests to pass for a release is a reasonable aim. You have. It's only bin/test-ztk that passes. bin/test-zopeapp still has a number of failures. There is also the zope.testing failure where a doctest tries to drive the pdb module: 2.7 added a new intermediate (private) method to the call stack in unittest's 'assertEqual', which causes that test to fail. That shouldn't be too difficult to fix; zope.testing already uses quite a few regexp-based renormalizers to hide traceback elements that differ in different Python versions. (Debugging those is a pain, though.) Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
On Tue, Jul 13, 2010 at 14:46, Hanno Schlichting ha...@hannosch.eu wrote:
On Tue, Jul 13, 2010 at 7:05 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
And I'm not disagreeing with the policy, but it can be argued that
depending on the location of *data* files inside the Zope2 package is
not necessarily relying on guarantees on internals.
I'd call anything that relies on a specific file system layout to be
internals. We only make guarantees on the semantics of the Python
import system, not how packages and modules are stitched together in
distributions and end up on the file system.
Considering that the Zope source code has a dozen examples of
App.ImageFile.ImageFile being used without a prefix (ex. OFS.misc_),
I think third party developers should be excused to think they could
follow the lead and expect their packages not to break during a stable
series.
I still think we should give them at least the 2.12 series to stop
using ImageFile incorrectly without breaking their code, but I won't
belabor the point any longer.
Obviously. Still, App.ImageFile.ImageFile (and any other Zope2 APIs
that do rely on software_home) should give a clear warning when
software_home is assumed, since it is the one assuming it. The
exception raised by the ImageFile call now gives no clue on what
actually went wrong and what a developer should do about it.
I agree with that. I thought the call to software home was being made
inside ZMySQLDA and not in Zope 2 code.
The attached patch adds such a warning, and also reveals where Zope2
commits the same sins. If there are no objections I'll commit it to
2.12 and trunk.
Finally, I'd like to ask that, when major changes land in a stable
series (like the spinning off of a whole package), that we allow at
least a week or two to pass before making a release, so people who
have test runners for their apps running against a stable repository
branch have time to adapt to the changes
Cheers,
Leo
Index: src/App/config.py
===
--- src/App/config.py (revisão 114644)
+++ src/App/config.py (cópia de trabalho)
@@ -36,7 +36,7 @@
def setConfiguration(cfg):
Set the global configuration object.
-Legacy sources of common configuraiton values are updated to
+Legacy sources of common configuration values are updated to
reflect the new configuration; this may be removed in some future
version.
Index: src/App/tests/testImageFile.py
===
--- src/App/tests/testImageFile.py (revisão 0)
+++ src/App/tests/testImageFile.py (revisão 0)
@@ -0,0 +1,28 @@
+import unittest
+import App
+from Testing.ZopeTestCase.warnhook import WarningsHook
+
+
+class TestImageFile(unittest.TestCase):
+
+def setUp(self):
+# ugly: need to save the old App.config configuration value since
+# ImageFile might read it and trigger setting it to the default value
+self.oldcfg = App.config._config
+self.warningshook = WarningsHook()
+self.warningshook.install()
+
+def tearDown(self):
+self.warningshook.uninstall()
+# ugly: need to restore configuration, or lack thereof
+App.config._config = self.oldcfg
+
+def test_warn_on_software_home_default(self):
+App.ImageFile.ImageFile('App/www/zopelogo.jpg')
+self.assertEquals(self.warningshook.warnings.pop()[0],
+ App.ImageFile.NON_PREFIX_WARNING)
+
+def test_suite():
+return unittest.TestSuite((
+unittest.makeSuite(TestImageFile),
+))
Index: src/App/ImageFile.py
===
--- src/App/ImageFile.py (revisão 114644)
+++ src/App/ImageFile.py (cópia de trabalho)
@@ -18,6 +18,7 @@
import os.path
import stat
import time
+import warnings
from AccessControl.SecurityInfo import ClassSecurityInfo
from Acquisition import Explicit
@@ -34,6 +35,13 @@
os.path.join(os.path.dirname(Zope2.__file__), os.path.pardir)
)
+NON_PREFIX_WARNING = ('Assuming image location to be present in the Zope2 '
+ 'distribution. This is deprecated and might lead to '
+ 'broken code if the directory in question is moved '
+ 'to another distribution. Please provide either an '
+ 'absolute file system path or a prefix. Support for '
+ 'relative filenames without a prefix might be '
+ 'dropped in a future Zope2 release.')
class ImageFile(Explicit):
Image objects stored in external files.
@@ -43,9 +51,12 @@
def __init__(self, path, _prefix=None):
import Globals # for data
if _prefix is None:
-_prefix=getattr(getConfiguration(), 'softwarehome', PREFIX)
+_prefix=getattr(getConfiguration(), 'softwarehome', None) or PREFIX
+if not os.path.isabs(path):
+
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas wrote: On Tue, Jul 13, 2010 at 10:01:35AM -0400, Tres Seaver wrote: Hanno Schlichting wrote: On Tue, Jul 13, 2010 at 3:23 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: what's the time frame for ZTK 1.0? I put that info into the post scriptum of my mail. Have I missed a mail with more failures? I would have thought getting those tests to pass for a release is a reasonable aim. You have. It's only bin/test-ztk that passes. bin/test-zopeapp still has a number of failures. There is also the zope.testing failure where a doctest tries to drive the pdb module: 2.7 added a new intermediate (private) method to the call stack in unittest's 'assertEqual', which causes that test to fail. That shouldn't be too difficult to fix; zope.testing already uses quite a few regexp-based renormalizers to hide traceback elements that differ in different Python versions. (Debugging those is a pain, though.) Can't be renormalized, as the pdb session requires sending an extra 'u' to get to the expected stack frame (it's a dumb test, FWIW). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw854MACgkQ+gerLs4ltQ4nSACg0y6g7ZuAJaw7H3nFAFqBWAws FvAAnjEaVCDoEhl/XzivN8XgTVfl7Qnu =8ERm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Can ZTK 1.0 support Python 2.7?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charlie Clark wrote: Am 13.07.2010, 20:48 Uhr, schrieb Christian Zagrodnick c...@gocept.com: Actually I was thinking about the individual packages. I assume dropping Python 2.4 should bump the respective package version at least from 1.x.y to 1.x+1.0, right? ZTK 1.1 will officially not support Python 2.6 but it won't seek to actively break 2.4 and 2.5. It sounds like you are suggesting what to do about packages that definitely don't work with 2.6. While I would have thought a syntax change shouldn't mean a major version, breaking compatibility obviously warrants some thought. But then I wouldn't expect a release just based on new syntax. Have you got a specific example in mind? I would say that a release of a ZTK package which drops support for a Python version still supported by ZTK 1.0.x should get a second-level version bump: that is the best possible signal that it is not a candidate for inclusion in ZTK 1.0.x+1. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw86AgACgkQ+gerLs4ltQ4seQCfayQ3RC8Hf2UNWtFa+qshsfsT 5PUAoL7A2T1thC/nxb+wotPZsqXR2Rjd =cDFb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
Hi all. Sorry if this is a little OT, but maybe someone could be interested: `Liberologico Srl http://www.liberologico.com`__ (Pisa, PI, Italy) **Job Description**: Senior Software Developer Liberologico is looking for an developer with good experience in Zope and Python. The developer will be responsible for porting a large IT application developed with the Zope/Python/PostgreSQL stack to a cloud environment. **What we expect you know** * computer science degree or better; * OOA/D (we expect at least you know use cases, design patterns and UML); * Python as an OOA/D language (not just for making scripts; we've a large and complex application); * Zope, when developing Python-based products (not just TTW applications); * IDE tools (emacs does not count as an IDE; vi* neither; Eclipse+PyDev is preferred); * Subversion and other version control systems (merge and branches, tracking third-party code); * PostgreSQL (a little more than making queries like you would do with any other database); * Linux system administration (you know how to make a script executable on a Linux, don't you?); * Test-driven development * Unit-testing **Where the work will take place** * Centro Polaris (http://www.sardegnaricerche.it/), Pula, Cagliari, Italy **Contact Info:** * **Contact**: Marco Bizzarri * **E-mail contact**: m.bizza...@liberologico.com * **No telecommuting** == -- Marco Bizzarri http://code.google.com/p/qt-asterisk/ http://notenotturne.blogspot.com/ http://iliveinpisa.blogspot.com/ ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/ Zope developer in Pula, Cagliari (CA), Italy
On Tuesday, July 13, 2010, Marco Bizzarri wrote: * IDE tools (emacs does not count as an IDE; vi* neither; Eclipse+PyDev is preferred); I am usually not commenting on things like that, but: What a turn off! This is one of the worst requirements I have ever seen. ;-) Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
On Tue, Jul 13, Stephan Richter wrote: On Tuesday, July 13, 2010, Marco Bizzarri wrote: * IDE tools (emacs does not count as an IDE; vi* neither; Eclipse+PyDev is preferred); I am usually not commenting on things like that, but: What a turn off! This is one of the worst requirements I have ever seen. ;-) Yeah, that one had me shaking my head as well ... \\kristian -- ... et nemo ex vobis interrogat me: »Quo vadis?« ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
On Tue, Jul 13, 2010 at 1:44 PM, Kristian Thy t...@42.dk wrote: On Tue, Jul 13, Stephan Richter wrote: On Tuesday, July 13, 2010, Marco Bizzarri wrote: * IDE tools (emacs does not count as an IDE; vi* neither; Eclipse+PyDev is preferred); I am usually not commenting on things like that, but: What a turn off! This is one of the worst requirements I have ever seen. ;-) Yeah, that one had me shaking my head as well ... \\kristian -- ... et nemo ex vobis interrogat me: »Quo vadis?« Well, it's interesting to see such a reaction; we've seen steep learning (and adapting) curve from an emacs/vi environment to an IDE like Eclipse; since we're a development shop working on Eclipse for all our projects (Java, PHP, Python), we required knowledge and practice of such a tool. Anyway, I assure no emacs/vi guy got injured in writing this requirement ;) Regards Marco -- Marco Bizzarri http://code.google.com/p/qt-asterisk/ http://notenotturne.blogspot.com/ http://iliveinpisa.blogspot.com/ ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Bizzarri wrote: Anyway, I assure no emacs/vi guy got injured in writing this requirement ;) Nope, but we had our morning fun :) Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw8WXAACgkQCJIWIbr9KYzf1QCffPZVzp/KYU+82/GQKjtvElDu CaYAoNkFL4w1d6+AZfUqf6njD3Y+4DDr =8tGf -END PGP SIGNATURE- attachment: lists.vcf___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
+---[ Marco Bizzarri ]-- | | Well, it's interesting to see such a reaction; we've seen steep learning (and adapting) curve from an emacs/vi environment to an | IDE like Eclipse; since we're a development shop working on Eclipse for all our projects (Java, PHP, Python), we required | knowledge and practice of such a tool. | | Anyway, I assure no emacs/vi guy got injured in writing this requirement ;) If your IDE is so awful that you need to specifically mention that your new developers know how to use it, I think you need a new IDE, because that one is not doing its job d8) -- Andrew Milton a...@theinternet.com.au ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
Marco Bizzarri wrote: I won't start a religious war on IDE editors :) You already did by putting such a ridiculous requirement in a job ad. Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
On Tue, Jul 13, 2010 at 4:58 PM, Chris Withers ch...@simplistix.co.ukwrote: Marco Bizzarri wrote: I won't start a religious war on IDE editors :) You already did by putting such a ridiculous requirement in a job ad. Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk As I said before, I've no interest in starting such a war; you find this is a ridiculous requirement: fine, you're more than entitled to have your opinion. Regards Marco -- Marco Bizzarri http://code.google.com/p/qt-asterisk/ http://notenotturne.blogspot.com/ http://iliveinpisa.blogspot.com/ ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] [JOB][OT?] Position for a Python/Zope developer in Pula, Cagliari (CA), Italy
On 13 July 2010 11:20, Marco Bizzarri marco.bizza...@gmail.com wrote: On Tue, Jul 13, 2010 at 4:58 PM, Chris Withers ch...@simplistix.co.uk wrote: Marco Bizzarri wrote: I won't start a religious war on IDE editors :) You already did by putting such a ridiculous requirement in a job ad. Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk As I said before, I've no interest in starting such a war; you find this is a ridiculous requirement: fine, you're more than entitled to have your opinion. I think what the senior developers react to here isn't the particular choice. You could have written Vim is preferred and people would still think: Do they want me to write with my left or right hand or do they want me to get the job done. Anyway, best of luck Marco! Regards Marco -- Marco Bizzarri http://code.google.com/p/qt-asterisk/ http://notenotturne.blogspot.com/ http://iliveinpisa.blogspot.com/ ___ Zope maillist - z...@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com fun crosstips.org ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-CMF] CMF Tests: 4 OK
Summary of messages to the cmf-tests list. Period Mon Jul 12 12:00:00 2010 UTC to Tue Jul 13 12:00:00 2010 UTC. There were 4 messages: 4 from CMF Tests. Tests passed OK --- Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux From: CMF Tests Date: Mon Jul 12 21:49:12 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013277.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux From: CMF Tests Date: Mon Jul 12 21:51:12 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013278.html Subject: OK : CMF-2.2 Zope-2.12 Python-2.6.5 : Linux From: CMF Tests Date: Mon Jul 12 21:53:12 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013279.html Subject: OK : CMF-trunk Zope-2.12 Python-2.6.5 : Linux From: CMF Tests Date: Mon Jul 12 21:55:12 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013280.html ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
