Re: [Zope-dev] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2013 11:33 AM, GitHub wrote: Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy! Woohoo! Nice work. BTW, how did you break the import cycle due to the zope.location monkeypatch? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE9/poACgkQ+gerLs4ltQ41BgCggEXl0utNEQAydRv1rws1xPrt +28AoJZvfxTNgRvKBhHXstxxDvTzcurE =2XB9 -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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Monday, March 11, 2013 11:56:10 AM Tres Seaver wrote: Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy! Woohoo! Nice work. BTW, how did you break the import cycle due to the zope.location monkeypatch? I moved the patch to __init__.py. I know, not zope.location.LocationProxy gets fixed up all the time instead of waiting for decorator to be imported. But it did break the cycle. 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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2013 02:02 PM, Stephan Richter wrote: On Monday, March 11, 2013 11:56:10 AM Tres Seaver wrote: Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy! Woohoo! Nice work. BTW, how did you break the import cycle due to the zope.location monkeypatch? I moved the patch to __init__.py. I know, not zope.location.LocationProxy gets fixed up all the time instead of waiting for decorator to be imported. But it did break the cycle. I was thinking of adding a ZCML directive which did the monkey patch (so that it wouldn't happen at import time at all). BTW, I merged the branch to the trunk and made a zope.security 4.0.0b1 release just now. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE+G9cACgkQ+gerLs4ltQ4J2wCdEJzJ2D4eIKZWxlmNdbJZyVgh mV0AoMIvVLKGZ6y/cgkoBz88w+iYbs0T =tf3G -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] Version Numbering for Ported Packages
Hi everyone, Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres wanted 4.0.0 to also have PyPy support, so he only did an alpha release to unblock the porting effort. Today, I finished the PyPy support and he released 4.0.0b1. * ZODB: We currently do not have a release for a ported ZODB. For any package requiring the ZODB directly or indirectly, we added a snapshot sdist of the py3 branch into the package to demonstrate the tests passing. (See the zodb- dev mailing list for the current status.) Of course, the alpha releases are really stable, all the tests pass under Python 2.6 and 2.7. 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 )
[Zope-dev] zope-tests - FAILED: 10, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-10 00:00:00 UTC and 2013-03-11 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received [1]Still Failing - zopetoolkit_trunk - Build # 199 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [5]winbot / z3c.layer.ready2go_py_265_32 [6]winbot / z3c.menu.ready2go_py_265_32 [7]winbot / z3c.pagelet_py_265_32 [8]winbot / zope.app.authentication_py_265_32 [9]winbot / zope.app.http_py_265_32 [10] winbot / zope.app.publication_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 199 https://mail.zope.org/pipermail/zope-tests/2013-March/073214.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073213.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073230.html [4]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073212.html [5]FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073210.html [6]FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073231.html [7]FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073211.html [8]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073229.html [9]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073227.html [10] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073228.html ___ 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] Version Numbering for Ported Packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2013 08:40 PM, Stephan Richter wrote: Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres wanted 4.0.0 to also have PyPy support, so he only did an alpha release to unblock the porting effort. Today, I finished the PyPy support and he released 4.0.0b1. If that release doesn't bust anything over the next day or two, I will likely push out a 4.0.0 final by the end of the week. I have one question: the zope.location import-time monkeypatch is a wart in zope.security: could we add a ZCML directive for doing that at configuration execution time instead? * ZODB: We currently do not have a release for a ported ZODB. For any package requiring the ZODB directly or indirectly, we added a snapshot sdist of the py3 branch into the package to demonstrate the tests passing. (See the zodb- dev mailing list for the current status.) We are essentially blocked on figuring out how to deal with instance / moudle attribute names in pickles: they need to be native strings under both Python2 and Py3k. I'm pretty hopeful that Pycon will let us figure that out. Of course, the alpha releases are really stable, all the tests pass under Python 2.6 and 2.7. I'm agreed for the most part. Can we make it a priority to fix the failing nightly tests? Also, is somebody running / reporting tests via Travis? Where are those results going? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE+jm8ACgkQ+gerLs4ltQ7Q8QCghZgjXHdpaCZ0zay2cvrY6N1o oUAAoJA9rptCLM1JAszEv93MfF7qghrq =1jPL -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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Monday, March 11, 2013 02:00:55 PM Tres Seaver wrote: BTW, I merged the branch to the trunk and made a zope.security 4.0.0b1 release just now. Yep, saw that. There are some uncovered lines for which I have to add tests left. Also, I just noticed while prorting zope.publisher to PyPy that proxies cannot be adapted, which is a big issue for any view libraries. 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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2013 10:29 PM, Stephan Richter wrote: On Monday, March 11, 2013 02:00:55 PM Tres Seaver wrote: BTW, I merged the branch to the trunk and made a zope.security 4.0.0b1 release just now. Yep, saw that. There are some uncovered lines for which I have to add tests left. Also, I just noticed while prorting zope.publisher to PyPy that proxies cannot be adapted, which is a big issue for any view libraries. Ouch. That lying about my type bit is hard to get over. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE+k/oACgkQ+gerLs4ltQ6wWwCfWvfDbILY76o51rmRsdaJ7390 yx0An3Qyrc7VO53TtOSt1WSllDwdBYb4 =+4m5 -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] zope generations updating objects with method name change
Hello Tres, Thanks for the reply. On Sun, 2013-03-10 at 23:32 -0400, Tres Seaver wrote: Method names are not stored in the ZODB at all: only the instance attributes are stored. Apologies. I've reported it wrong. I was not able to reproduce the problem after a fresh start. -- Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in signature.asc Description: This is a digitally signed message part ___ 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 )
