Re: [Zope-dev] svn.zope.org issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2013 08:21 AM, yuppie wrote: Hi! Where can I report problems with svn.zope.org? For some days now I have trouble making checkins. Commits are successful, but somewhere in the post commit hook things go wrong. No mail is send to the checkins list and my svn client freezes - I guess because the server doesn't signal the commit is finished. Other people seem to have the same issue, the last checkin mail to the list was sent 2013-09-17. The ZF infrastructure committee is working on moving SVN to a new host. Report problems to infrastruct...@zope.org. 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJYMb0ACgkQ+gerLs4ltQ7SKwCgmACy6IPOT1eCX/LTIs2lcLQC 22sAoL2rCgelzJ9hd3BDhE8NQBj+BbfA =/Wgl -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-tests - FAILED: 1, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/08/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079153.html Transient github failure: fatal: unable to connect to github.com: github.com[0: 192.30.252.131]: errno=No such file or directory 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJVnpwACgkQ+gerLs4ltQ5XZgCeIfK/wW6o97VFMRhtroymGOHl 2hEAnRtLOmPoaibbkYnl5nXrCCm7BcRK =IVBr -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-tests - FAILED: 1, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/01/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079033.html Failure in buildout phase:: Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.9 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJMdroACgkQ+gerLs4ltQ5MDgCdF5E7uAlCblkYBLgLjfJGf2du 4PAAoKHbJUGLQzUEhzH8EdWN8iaPNHVv =y37n -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] please move z3c.formwidget.query to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/22/2013 11:27 AM, Vincent Fretin wrote: Can someone please make a new release? Releases can be made only by one of: malthe, optilude, davisagli, laurencerowe, timo, esteele - -- === 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI/M3YACgkQ+gerLs4ltQ4aIQCeLTrcoCxUzDe3M3c98y9t4DmS LzYAoNWgpyb1W/LEXYDzWiWWZPD4YaHj =HrN6 -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-tests - OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/21/2013 07:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-09-20 00:00:00 UTC and 2013-09-21 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 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 Yay! 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI+Tq4ACgkQ+gerLs4ltQ57JQCfaojpXeeQCmMFhuAb5etsoePS zm0AnR8Q3FYxrsqnfUFu6V/VVU9KxPH0 =ztKD -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-tests - FAILED: 6, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/18/2013 06:40 AM, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. FWIW, WebTest 2.0.9 went out Wednesday: https://pypi.python.org/pypi/WebTest/2.0.9 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/ iEYEARECAAYFAlI8UDAACgkQ+gerLs4ltQ7ElgCePY2PC6fHHpf9p/jZAXWZdYe5 ThMAoIyTyVjI8PzbERIPVKMpKhK4KTop =Gnik -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-tests - FAILED: 4, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/09/2013 11:53 AM, Marius Gedminas wrote: On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest? 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/ iEYEARECAAYFAlIt9rkACgkQ+gerLs4ltQ4G+ACeJA6XZdZzR0EXWWWuiHAGJNTY TPQAnAgR9Uj3L1IqT5a1+sLrDugHAF8c =vHtg -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-tests - FAILED: 1, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/08/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html Same failure as yesterday:: Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 Odd that the other three cleared up (or didn't they run?) 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/ iEYEARECAAYFAlItMpcACgkQ+gerLs4ltQ599gCffh0g1nBUURxpDXFFEoaupA2+ uPIAoLWsd3X8o4UR3tU3nXDo/J8xaAtB =1TqS -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-tests - FAILED: 4, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: - % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 - % --- 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/ iEYEARECAAYFAlIrxFgACgkQ+gerLs4ltQ4R+QCfTmElgT9bLTKi//6JtRWoZ17S +l8An2nWUfe7sGMijMkDqSAVIeMH5A6/ =E0GF -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-tests - FAILED: 9, OK: 11
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. 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/ iEYEARECAAYFAlIn1y4ACgkQ+gerLs4ltQ7wbgCfQm179NVXtzqG6reuHXLM09Us 3IYAnR8WFF9mFvoW/a5fS+Hq4VSbrZy8 =be6K -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-tests - FAILED: 10, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/27/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078456.html [2]FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078457.html [3]FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078455.html [4]FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078458.html [5]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078453.html [6]FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078454.html [7]FAILED winbot / zope.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078450.html [8]FAILED winbot / zope.principalregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078451.html [9]FAILED winbot / zope.site_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078449.html [10] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078452.html All failed during the 'git' phase: fatal: unable to connect to github.com: github.com[0: 204.232.175.90]: errno=No such file or directory 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/ iEYEARECAAYFAlIdTWwACgkQ+gerLs4ltQ6UNgCfZxr7bKzF4ZNA2kTpWXfhawGd ccoAoNM1HBXwqqVHEgZdJgE3BZe6OA+E =HWX+ -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-tests - FAILED: 3, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/29/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/078036.html [2]FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/078034.html [3]FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/078035.html All three fail so: - - % -- Building lxml version 3.2.3. Building without Cython. ERROR: 'xslt-config' is not recognized as an internal or external command, operable program or batch file. ** make sure the development packages of libxml2 and libxslt are installed ** - - % -- 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/ iEYEARECAAYFAlH3BpgACgkQ+gerLs4ltQ7NUACgtrho5hAck9WVyIPNxfbYIUIm HpEAoMvh5fhL1tByAcGLoZiynYFjw9IZ =UeqT -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-tests - FAILED: 3, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/19/2013 02:21 AM, Marius Gedminas wrote: [3]FAILED winbot / zope.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077887.html While: Installing. Getting section tox. Error: The referenced section, 'tox', was not defined. A simple mistake in buildout.cfg. Fixed. Ouch, that was my bad. (I don't know why it took more that a week to show up, though). Thanks for the fix! 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/ iEYEARECAAYFAlHpqpsACgkQ+gerLs4ltQ4Z0ACgvwEKIfaAS3ypJSDfXhQDF0/8 OmoAoIHcUzynYKbQ1/J3fhKtiaj1D37A =oYNG -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-tests - FAILED: 5, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/16/2013 06:53 AM, Marius Gedminas wrote: Perhaps manually installing setuptools = 0.7 into c:\python2*_64 would fix the failing builds? +1. Let's just get past the distribute / old setuptools mess and get on with our lives. 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/ iEYEARECAAYFAlHl0ncACgkQ+gerLs4ltQ4OnwCeMQxGaJC2DPeibq1mGbf4iTqW 2fsAoKvfK1zVOD7LY9vqbC8i2sCr7/Ju =yL1D -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-tests - FAILED: 14, OK: 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/11/2013 03:55 AM, Patrick Gerken wrote: now I have to create a virtualenv with --distribute, then I have to upgrade setuptools We should be upgrading all our projects to zc.buildout 2.2, which drops 'distribute'. 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/ iEYEARECAAYFAlHexM0ACgkQ+gerLs4ltQ6wyQCgkrbTYpPBYdzsJC4nE1ME+UgB ZvQAnjvNL0CRY5Td7DcWdxhNa0ySIwLo =yMRe -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-tests - FAILED: 14, OK: 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/11/2013 01:05 PM, Wichert Akkerman wrote: FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but had to revert to a buildout 1.x due to conflicts with an OS-provided pkg-resources sourced from distribute that I could not uninstall. Patient: Doctor, when I drink iced tea I get a cold stabbing pain in my eye! Doctor: Take out the spoon! (In other words, if the system python is hosing you, quit using it). If the system python provide command-line flags for suppressing site-paacakges, you might be able to use them to bootstrap. Or build a virtualenv '--without-setuptools' and use that to boostrap. Or just build your own Python and be done. 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/ iEYEARECAAYFAlHfT/EACgkQ+gerLs4ltQ44JQCePWPiYBa4hG1RP+XlwAAxigVq 0jYAn0PkuUFKTaG6kpWCMh3F4DA0NViD =nDCl -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] Maintenance of zope mailman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2013 02:16 AM, Patrick Gerken wrote: last month, all Mailing lists were unavailable for a week. On twitter, I saw it took some time to set up due to time constraints. Are there plans to increase the admin team to avoid time constraint issues? Yes, indeed. There is a new infrastructure committee, and an associated mailing list for it, consisting of the voumnteers who are managing the foundation's hosts and services. Regarding Mailman itself, after we lost regular cmf tests, I set up my jenkins to run tests for CMF too. Unfortunately I cannot send mails to the cmf-tests mailing list. My subscription request from 5.5. is still in the moderation queue. Do we still have moderators for mailman? I approved that request. I expect that both services do not involve a lot of ongoing work. The administration is probably time intensive in the beginning to get to know how everything is set up. If thats the case I happily volunteer. Thank you for volunteering! I just now sent you a Mailmn invitation to the infrastructure list. Please accept and we can work out the details on that list. 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/ iEYEARECAAYFAlHTCbkACgkQ+gerLs4ltQ79AACfcrz6XvLNrqdNaP0HkRRbBgLS o4kAoNkP6UN9gvCKQDW2G67fYgOdwIe6 =/jNU -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] PyPI ownership
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If somebody is running a script which is auto-adding me as a PyPI owner to every ZF-owned package under the sun, please stop: I've removed myself now twice from all the 'zope.app.*' packages. 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/ iEYEARECAAYFAlHRpV8ACgkQ+gerLs4ltQ7j4wCfdVjPf3k90sW8jY3P3ZdgOSx5 cq8AnjGx8Tk8Xhi1pqUkhE4WMLg7yEPm =YczZ -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] RFC: branch updating zc.buildout and bootstraps to use setuptools 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/2013 10:13 AM, Leonardo Rochael Almeida wrote: On Mon, Jun 3, 2013 at 10:25 PM, Tres Seaver tsea...@palladion.com wrote: [...] I would like some help getting the manuel + renormalizer + doctest tests working, or at least getting the spurious output differences smoothed away so we can see real semantic changes, if any. Which tests do you need help with? zc.buildout ones on your branch or Zope repo projects running with your branch? I need help with the buildout tests themselves: the combination of manuel + regext nromalizers + doctests makes my head hurt. If the former, wouldn't it be better to (also) contact the buildout development list [1]? Ugh, Google Groups I guess that is the right place to ask, though; I had forgotten that there was a separate list. If the latter which steps do we need to follow to get to the failures you need help with? [1] https://groups.google.com/forum/?fromgroups#!forum/buildout-development I haven't gotten far enough with it to try building the ZTK projects, etc. It needs to pass its own tests first. 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/ iEUEARECAAYFAlGuAYYACgkQ+gerLs4ltQ4rIQCXR0lHLq9vSgbFLgljbl+ws1uL 9QCgtdLevOwQtbVTYm8Z8/fIFuWgkIk= =PRCv -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-tests - FAILED: 86, OK: 5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads 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/ iEYEARECAAYFAlGsjhoACgkQ+gerLs4ltQ4+SACglPxJ5J5b7eJV5yUfADFVjeAR bJsAoNJYhnaciMoGMqkP14KRGsFiO7ux =qGub -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-tests - FAILED: 86, OK: 5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2013 09:04 AM, Adam GROSZER wrote: On 06/03/2013 02:37 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads I think it's the first. It seems to be a distribute vs setuptools fight. I recently installed distribute in site-packages, but that does not seem to help. Would it help to update to setuptools-0.7 in the 'site-packages' (removing distribute completely)? I have the feeling that the faster we put setuptools-0.6 and distribute behind us, the better off we will be. I've played with it some this morning: the major issue for our buildouts is to get an 'ez_setup.py' selected which doesn't look for setuptools-0.7 on PyPI -- I don't quite know why, but it is only available here: https://bitbucket.org/pypa/setuptools/downloads The attached file woks for me using e.g.: $ /path/to/python bootstrap.py --setup-source=file:///tmp/ez_setup.py 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/ iEYEARECAAYFAlGsr2oACgkQ+gerLs4ltQ4fcwCcCKice5D4MObbCuUEkeq88AT3 F+UAoI5Jlfwa44MsmfpPOO4Z1i9kVfO0 =Iiof -END PGP SIGNATURE- ez_setup.py 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 )
[Zope-dev] RFC: branch updating zc.buildout and bootstraps to use setuptools 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The bloody state of the winbot at the moment seems tied to issues related to setuptools 0.6, distribute 0.5.4x, and zc.buildout. I put in some effort today on a branch to end-run the whole old-setuptools / distribute bit by updating buildout2 to use the newly-availabe (but not yet released to PyPI) setuptools 0.7. This version is the first release after the merge of old setuptools and distribute, and should be the preferred target for future work. My branch of buildout is here: https://github.com/tseaver/buildout/tree/use-setuptools-0.7 with a pull request to the main repo: https://github.com/buildout/buildout/pull/123 One issue that has to be worked around in the near term: the 0.7 release has been published via the bitbucket downloads page: but not pushed to the cheeseshop. I uploaded a hacked version of 'ez_setup.py' to deal with that interim problem here: http://dist.repoze.org/ez_setup-0.7.py and my buildout branch uses that version. I would like some help getting the manuel + renormalizer + doctest tests working, or at least getting the spurious output differences smoothed away so we can see real semantic changes, if any. I'm assuming that it will take some days (weeks?) to get them passing, by which point we can hope that the 0.7 release has been pushed to PyPI (relieveing the need for a double-secret version of 'ez_setup.py'). Thoughts? 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/ iEYEARECAAYFAlGtQgUACgkQ+gerLs4ltQ59zwCeOScg3hciUGN3IyAltHfM0+eS x/QAoMlUvQ5ifgiWnhuyQXqqdcP3Jjag =BbxG -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-tests - FAILED: 81, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/28/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Failure - zopetoolkit_trunk - Build # 278 https://mail.zope.org/pipermail/zope-tests/2013-May/075192.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 279 https://mail.zope.org/pipermail/zope-tests/2013-May/075193.html These are both failures against PyPI, likely due to the recent CDN / https only changes there. I think the rest are likely the same. 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/ iEYEARECAAYFAlGlZvIACgkQ+gerLs4ltQ4OkACfengs86pQXkVEJ+VyRs0eWayz H8cAnRK31Y/6orQgcWCtTHd/ozwHqvgC =+Fbv -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-tests - FAILED: 3, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/21/2013 06:28 AM, Marius Gedminas wrote: [1]Still Failing - zopetoolkit_trunk - Build # 270 One zope.session failure: File /var/lib/jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.session/src/zope/session/http.py, line 442, in zope.session.http.CookieClientIdManager.setRequestId Failed example: expires now + timedelta(0, 55 * 60) Expected: True Got: False Hmm, I changed that yesterday because the old test code (using 'time.mktime') was failiing on my box, likely due to an odd mix of naive and GMT times. The *actual* cookie being set by the code-under-test is correct -- we just have a problem writing good assertinos about it. [2]winbot / ZEO_py_265_32 One failure: File c:\buildslave\zeo\build\src\ZEO\tests\testZEO.py, line 1162, in ZEO.tests.testZEO.client_has_newer_data_than_server Failed example: len(client_errors) = 2 Expected: True Got: False This is another place where I have tweaked the test code, trying to remove race conditions: the test is trying to make assertionas about errors being logged, and does a bunch of sleeping trying to ensure that enough stuff gets logged. Again, it is a bad test, and not a real issue with the code being tested. 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/ iEYEARECAAYFAlGbepAACgkQ+gerLs4ltQ56IACeIrEUbC/TC+Y0d+AvjVom6rID GkEAn2nNosl/7EhWpymlf2n/zcN6avi+ =ZYlR -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-tests - FAILED: 9, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/20/2013 01:57 AM, Marius Gedminas wrote: On Mon, May 20, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 269 Same old issue with sys.path lacking persistent. I fixed this by removing the checkouts of the non-ZTK packages from the buildout. I made this change after spending an hour this morning trying to isolate the differences between the way the working set was computed in the ZTK buildout vs. one of the failing packages (zope.traversing). In the end, I couldn't figure out why the presence of the '.egg-links' for persistent / BTrees / ZODB / ZODB3 / ZEO in the 'develop-eggs' directory was causing the breakgage, but I also lost my will to care. 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/ iEYEARECAAYFAlGaNk8ACgkQ+gerLs4ltQ4o+QCgj5gbqOSVo5mxV5spX39dnfu+ WzEAoM96PBxU0EMxAS6XewF5DpCm1Alw =U369 -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-tests - FAILED: 100, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/18/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-05-17 00:00:00 UTC and 2013-05-18 00:00:00 UTC: Jason fixed the distribute_setup.py link earlier tody (about four hours ago). The majority of the winbot tests should go back to green today. 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/ iEYEARECAAYFAlGYvVwACgkQ+gerLs4ltQ6fWwCg1kHBbb8Z0AEopPF8Hoit7z63 abgAn1691XdPvNyoF35nKlPdFy2wND8E =kD2q -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-tests - FAILED: 63, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/17/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074888.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074889.html [3]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074890.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074891.html The failure here is in a new test: I just pushed a '/' - os.path.sep fixup. The other 59 look to be the same distribute_setup.py calls out distribute 0.39 issue: http://python-distribute.org/distribute_setup.py CC'ing Tarek and Jason. 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/ iEYEARECAAYFAlGXpusACgkQ+gerLs4ltQ7lOQCgqcKskTTlwhAVaUSStUVufUtW VVEAmgOHxX3we9rmnoDNtWMG7suXUCgE =vNET -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-tests - FAILED: 79, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/15/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-05-14 00:00:00 UTC and 2013-05-15 00:00:00 UTC: See the footnotes for test reports of unsuccessful bui A sampling shows all these are tied up with the distribute has no cli.exe on Windows problem. 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/ iEYEARECAAYFAlGU9hsACgkQ+gerLs4ltQ6yggCeOSk3yKRrrGuEqgvOFW1jPd83 gMUAn3OAts5eZC/C43dogkK2P80maOpI =Vbf5 -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-tests - FAILED: 8, OK: 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/2013 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Still Failing - zopetoolkit_trunk - Build # 264
https://mail.zope.org/pipermail/zope-tests/2013-May/074326.html
I fixed an unpinned version for a new downstream dependency today. I
think that will get us back to failing due to persistent / BTrees
mismatches. :(
[2]FAILED winbot / ZEO_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074325.html
These tests are so slow and hard to work with that I lose patience with
them. It looks like the ZEO tests are re-using some ZODB doctests, but
without benefit of the renormalizers / checkers ZODB uses. I will look
at exposing those items in ZODB, and have the ZEO tests reuse them.
[3]FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2013-May/074335.html
[4]FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-May/074336.html
[5]FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2013-May/074337.html
[6]FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-May/074338.html
I whacked another couple of Windows-only moles this weekend
('ZODB.utils.u64' returning a 'long', some file-not-closed bugs I
introduced while trying to remove 'tempfile.mktemp'). I think I need
keys to the winbot, or at least the ability to kick off a test run
proactively.
[7]FAILED winbot / zope.app.content_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074339.html
[8]FAILED winbot / zope.interface_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074340.html
Github was offline.
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/
iEYEARECAAYFAlGO8LkACgkQ+gerLs4ltQ70RQCfap+HV93JBbFNNGy3M44NFZws
PXoAoNNTSrd+KhMzSo+p61Wnw7ozkrC1
=Oc7Q
-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-tests - FAILED: 5, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/10/2013 09:00 PM, Zope tests summarizer wrote: [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074321.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074322.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074323.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074324.html These are all Windows-only failures, due to my attempt to clean up the use of 'tempfile.mktemp': I have reverted that change, and expect those tests to pass 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/ iEYEARECAAYFAlGNz7kACgkQ+gerLs4ltQ4jSQCeOwKOlVul9Dykks4JyMeIozp8 jB0An0HW00rmSeXtKcsDGD0CNkdCIp2U =3zmJ -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-tests - FAILED: 4, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/25/2013 04:36 AM, Marius Gedminas wrote: On Thu, Apr 25, 2013 at 11:21:37AM +0300, Marius Gedminas wrote: On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [3]winbot / z3c.contents_py_265_32 Same old -- and I just managed to reproduce it at last. ZODB.utils.newTid(None) returns '\\x03\\x9e8\\x9a:\\x12\\x88', i.e. the repr of an 8-byte string instead of the 8-byte string itself. AFAICT it's because repr(persistent.timestamp.TimeStamp(2013, 04, 25, 11, 30, 0)) changed in persistent 4.0.5: https://github.com/zopefoundation/persistent/commit/e692af8281466fa309aae9273864039dcb287383 This was fixed in ZODB 4.0.4a4: https://github.com/zopefoundation/ZODB/commit/8dfbff499d109b1cf86d1b4b2b98a6cf8d17ce43 https://github.com/zopefoundation/ZODB/commit/994af0c5f9df63d403a0e21d80eec51d69686bc4 https://github.com/zopefoundation/ZODB/commit/19e851c2230a20cfcebc68fca37ce2c0bb716b92 https://github.com/zopefoundation/ZODB/commit/2ce7b945003ca8494f970a6946e4143dc18848e6 So latest stable ZODB3 (3.10.5) is incompatible with the two latest stable persistent releases (4.0.5 and 4.0.6). What should we do? Release ZODB3 3.10.6 with a backport of these patches? ZODB 3.10 bundles its own version of persistent: the standalone one shouldn't be used at all if ZODB 3.10 is in play. 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/ iEYEARECAAYFAlF5NGgACgkQ+gerLs4ltQ5EmgCbBmbeaDMs/6pyN0SQc3jcIlzj AakAoLwmtyjODMmz3JXHxGXy8rUMElAl =5GSE -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.lifecycleevent dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2013 11:59 AM, Souheil CHELFOUH wrote: Hello all, I've been poking the dependencies of several zope packages and it appears that : zope.interface = 4.0 contains IObjectEvent and its implementation ObjectEvent zope.component = 4.0 contains import of IObjectEvent and ObjectEvent zope.lifecycleevent = 4.0 imports IObjectEvent and ObjectEvent from zope.component, and doesn't import anything else from this package, only in the tests. We could free zope.lifecycleevent from the zope.component dependency, making it a test dependency only +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.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFu7FsACgkQ+gerLs4ltQ5oRACeK73oh/ihQznzvx/JfZIRZYPI rREAoL96RAeVFu4S86Hi/OSCdO4vS70u =DzI1 -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-tests - FAILED: 3, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/06/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 225 https://mail.zope.org/pipermail/zope-tests/2013-April/073719.html AFACT, these failures are bugs in z3c.recipe.compattest: it is generating the test scripts without full expanding the transitive depencencies of the tested packages. None of the separate buldouts 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.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFhkIIACgkQ+gerLs4ltQ7xhgCg3NkGvCxl0Qf0L4TcNFO6Ejz5 SYoAn0yl8eG53jrb9PIXcDXEZSsn93zq =se8y -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-tests - FAILED: 8, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html Ugh. I think Marius had some clue to this one, but I'm baffled. [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html Looks like more renormalizer fun. [8]FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html Network failure during 'git pull'. 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/ iEYEARECAAYFAlFdvFgACgkQ+gerLs4ltQ50KACeI7zMeX6JqKFBVjhfzH+r9l0b piMAoNVY+Mf+dAF1HvVDAHhvqRxISaj7 =O1Bu -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-tests - FAILED: 6, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/01/2013 09:00 PM, Zope tests summarizer wrote: [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073653.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073654.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073655.html These all look to be a borked renormalizer: - -- Expected: Traceback (most recent call last): ... POSKeyError: 'No blob file at BLOB STORAGE PATH' Got: Traceback (most recent call last): File c:\Python26_32\lib\doctest.py, line 1253, in __run compileflags, 1) in test.globs File doctest blob_transaction.txt[150], line 1, in module blob_storage.loadBlob(blob._p_oid, s1) File c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\blob.py, line 645, in loadBlob raise POSKeyError(No blob file at %s % filename, oid, serial) POSKeyError: 'No blob file at c:\\buildslave\\ZODB_dev_py_265_win32\\build\\parts\\test\\tmp\\testwzejdj\\blobs\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x05\\0x039db52c5b76ebab.blob' - -- 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/ iEYEARECAAYFAlFa54YACgkQ+gerLs4ltQ5ragCgia5bO4cz2pIECPSM4x2ABeqo 8v8AoNbeyXGMpHipBQ22iA2qS3/XVze6 =OmZ3 -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-tests - FAILED: 7, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/29/2013 09:00 PM, Zope tests summarizer wrote: [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-March/073603.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-March/073604.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-March/073605.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-March/073606.html Due to re-adding UTF8 in the changelog -- the code in setup.py which tried to make that work was ugly and untested. Let's just leave MvL's name in its ASCII transcription, please. 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/ iEYEARECAAYFAlFXH+AACgkQ+gerLs4ltQ6FLQCgqC/MlOWJr9GERC+jVY7iRMB+ JZUAnAtS0rs9COMwDkexSigvrsOHHH/4 =rg0i -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] request for more package migrations to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2013 08:13 AM, Sebastien Douche wrote: On Fri, Mar 22, 2013 at 10:23 AM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: Here's the list: groktoolkit grokcore.errorview grokcore.permission grokcore.registries grokcore.resource grokui.admin hurry.query hurry.workflow z3c.bcrypt Don't understand why Grok packages (or 3rd party packages) must go on the Zope Foundation repos. By virtue of the contributor agreement, they are all ZF-owned (well, half-owned) projects. If there are projects which should be spun out of the Foundation, we have an open item for the repository committee to draft a procedure for such cases for the new board's action. 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/ iEYEARECAAYFAlFMYygACgkQ+gerLs4ltQ4P3QCgl8edHtniWOpbJ9cl+LjQ8Ha2 QC8An2Jeqd48OgW59RzX2Hd0yjuj+eUv =AXbC -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-tests - FAILED: 6, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/21/2013 03:11 AM, Marius Gedminas wrote: ValueError: _p_serial must be an 8-character bytes array So that's, you know, *interesting*. I've no clue, and also cannot reproduce locally. I wish we knew what `serial` actually was. That smells as though somehow the new 'persistent' module is being used, in spite of the fact that ZODB 3.10.x bundles its own version. The separately-released version is strict about non-bytes values as OIDs / TIDs. 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/ iEYEARECAAYFAlFLS7gACgkQ+gerLs4ltQ5AOwCfblpOaMpaUZM8v0u3/a4k2cDg 2cgAoJoHOpDuFCJLq5ygUC6633mHTY7p =pC8Z -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.container] 9100fc: Tagging 3.11.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2013 01:48 PM, Stephan Richter wrote: On Tuesday, March 19, 2013 08:38:23 AM GitHub wrote: Commit: b2ae9a9bd5e3dc214f13c6ae77fa06ad55102aba https://github.com/zopefoundation/zope.container/commit/b2ae9a9bd5e3dc 214f13c6ae77fa06ad55102aba Author: Matthew Wilkes g...@matthewwilkes.name Date: 2013-03-19 (Tue, 19 Mar 2013) Changed paths: M setup.py M src/zope/container/_zope_container_contained.c M src/zope/container/_zope_proxy_proxy.c Log Message: --- Comment out the C extension. This should build conditionally, but this is just for testing I have actually some pypy attempts in a local version as well. The big problem is that the ContainedProxy must inherit from zope.security.proxy.ProxyPy and zope.persistent.persistence.Persistent. Both of those classes define __slots__ so they cannot both be base classes. The only way to fix this, I think, is to change the Python implementation of the security proxy or Persistent to not have slots and only define the slots in a derived class. Please don't attempt to mess with the persistent class: the slots there are crucial to performance. 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/ iEYEARECAAYFAlFI1VEACgkQ+gerLs4ltQ4KHgCbBkreu1q7MT/FwYbHATZbCkdO oXsAoIAVLwX3JeEZHqfHEi9JUn6Hzpdy =SDMg -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] Version Numbering for Ported Packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2013 12:05 PM, Stephan Richter wrote: On Wednesday, March 13, 2013 11:31:10 AM Tres Seaver wrote: FWIW whenever I get a failure notification from Travis about a package that doesn't have a .travis.yml, I uncheck the Active checkbox in Github repo settings. Unless the project already passes all its tests when run manually from a checkout, please do not turn on any automated reporting. Having seventy or so of those messages show up directly in my inbox on a travel-to-Pycon day was major suckage. Please note that I always turn off E-mail notification for Travis in the config file. Marius mentioned to me this morning that the messages were due to having turned on Travis but the package not having a .travis.yml file. I have worked all morning to rectify that and add a .travis.yml to all ZF GitHub packages. The set of packages now migrated to Github (including zope.app.*, z3c.*) is far larger than the set which is actually being cared for. I didn't expect to see most of those packages migrate at all, because they are de facto abandoned (not used by Zope2, Grok, or any other active project). We only moved packages that are still checked by winbot and the pnes that we ported because we use them in our project. 250+ of them? OK, I retract my concern then, if you are actually using them. 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/ iEYEARECAAYFAlFAo2AACgkQ+gerLs4ltQ7NHACg14Y8J1ATNDjdiOEuKHlD+YJE DI0An0flX3L5TriqfWbIf5BKbu6LK4x3 =0/KI -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...
-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...
-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 )
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...
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2013 04:19 PM, Joshua Immanuel wrote:
My application is based on Grok. Whenver, I change a method-name or
add a method to a Model, Grok fails to load the previous version from
the ZODB. I resorted to writing simple generations (zope.generations)
to update the stored model objects.
For 'method name' changes, this basically means: 1. create new object
2. copy every single attribute of old-object to the new-object 3.
delete old-object 4. save new-object
How does everyone else do this? Or is there a way to make
grok/zope/zodb not persist the method-names and signatures in a
content component (grok Model)?
Method names are not stored in the ZODB at all: only the instance
attributes are stored.
What you report doesn't correspond with how ZODB is designed, nor with
how Zope has been using it forever. For instance, I can create a class
inside a module:, derived from Persistent:
# foo.py, v1
from persistent import Persistent
class Foo(Persistent):
def __init__(self, bar, baz):
self.bar = bar
self.baz = baz
and make instances of it, adding them to another persistent object:
from ZODB.DB import DB
from ZODB.FileStorage import FileStorage
db = DB(FileStorage('/tmp/data.fs'))
conn = db.open()
root = db.root()
from foo import Foo
root.foo = Foo('bar 1', 0)
import transaction
transation.commit()
and then later modify 'foo.py', adding methods to the Foo class
# foo.py, v2
from persistent import Persistent
class Foo(Persistent)
def __init__(self, bar, baz):
self.bar = bar
self.baz = baz
def spam(self):
return self.bar * self.baz
and still load the previously created object from the database::
from ZDOB.DB import DB
from ZODB.FileStorage import FileStorage
db = DB(FileStorage('/tmp/data.fs'))
conn = db.open()
root = db.root()
from foo import Foo
assert isinstance(root.foo, Foo)
print root.foo.spam()
If that isn't working for your models, you must be doing something very
weird. Possible issues:
- - Do your model classes derive from Persistent?
- - Do they have attributes with multable values (e.g., native Python dict
or list)? If so, does your code mutate those values without telling the
containing object it has changed?
- - Are you remembering to commit the transaction?
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/
iEYEARECAAYFAlE9UFkACgkQ+gerLs4ltQ6euQCeORe7UvO3a4VK8oAP+pvd7Rce
lL8An1TxxJcb48YjFa9Ih67U7N1Y57cl
=2eUa
-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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/08/2013 02:18 PM, Stephan Richter wrote: On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:15 PM, Tres Seaver wrote: The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. I put that work on a branch: https://github.com/zopefoundation/zope.security/tree/pure_python_proxy Likely I won't get back to it this week. Hi Tres, do you see yourself working on this again soon? I was going to port some packages to PyPy, but got quickly blocked by zope.security. No, I don't think I will be working on that package in the near future (I pushed changes merging the trunk and fixed the coverage today). 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/ iEYEARECAAYFAlE6S1AACgkQ+gerLs4ltQ75/ACbBoPUgnPVEFPBLorH5SRiYnXX vfIAmgKOsillJ0VLZzZsxsQ2L48z48PI =C34r -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-tests - FAILED: 11, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/07/2013 11:51 AM, Stephan Richter wrote: On Thursday, March 07, 2013 05:46:48 PM Marius Gedminas wrote: I'm not sure that's the right thing to do. Perhaps page templates, when given a file on disk with \r\n, should normalize the line endings to \n? Opinions? I think we should retain EOL characters as long as clients (i.e. browsers) understand them, which they do. With template source, tools may require platform-specific line endings. For rendered HTML / XML, no tool / browser that wants to work with the 'net at large can have such expectations, which makes preserving them a non-use-case. +1 to Marius' proposal to open template files with 'U' in the mode. 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/ iEYEARECAAYFAlE4yVoACgkQ+gerLs4ltQ6mEgCffTFzG8t0Pj1zMjSclJAo6bKE t5oAoMvDejWwpKceqfG5ilogZfJoIdXm =Yryz -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] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2013 10:34 PM, Arfrever Frehtes Taifersar Arahesis wrote: 2013-02-28 21:04:33 Tres Seaver napisa?(a): I have ported it to Python 3.2 and 3.3 and released a 4.0.0 version. There are still multiple problems (types.TupleType, sys.modules.has_key etc.): $ PYTHONPATH=src python3.3 -c import zope.sequencesort Traceback (most recent call last): File string, line 1, in module File /tmp/zope.sequencesort/src/zope/sequencesort/__init__.py, line 14, in module from zope.sequencesort.ssort import sort File /tmp/zope.sequencesort/src/zope/sequencesort/ssort.py, line 17, in module from types import TupleType ImportError: cannot import name TupleType Weird: the tests seemed to run, but only the 'coverage' section was actually running. I just released 4.0.1 which fixes the remaining test breakage under Py3k. 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/ iEYEARECAAYFAlE1DswACgkQ+gerLs4ltQ4kuwCffWRNVmRlWxJ1TEUOGMlFiRWV ZAUAoIcnx6EYG4EyiyxeNGmm7GWj+yFu =5NvX -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] Zope2 git mirror not updating?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2013 08:10 AM, Jens Vagelpohl wrote: On Jan 11, 2013, at 14:07 , Wichert Akkerman wich...@wiggy.net wrote: I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org. AFAICT, the git.zope.org mirroring process is not functioning. E.g., the 'py3' branch of ZODB is not there, lots of repositories are mssing altogether, etc. 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/ iEYEARECAAYFAlEyOjoACgkQ+gerLs4ltQ43zACfSKI/4kJt8qI7e88XHsp8FMug UmEAoLAME3K4UGEEC3s2Lam4srgZA68k =R8VZ -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] procedures for moving package to github and porting to Python 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/2013 08:50 AM, Stephan Richter wrote: On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote: Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. You mean the ZF mailinglist that only ZF members can join? Yeah, but if you are a committer, you are a member. :-) Not so. Foundation members are listed here: http://foundation.zope.org/members/nominated_members The original group of what are now called nominated members was invited from the then-existing set of committers, but there is no necessary tie between the two. 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/ iEYEARECAAYFAlEwtfMACgkQ+gerLs4ltQ66bwCfTubHRqqMv3PkZemQgXwoIx4s n10An3Jd/08Vp8k28xPqOZta6Bbj/GRM =vuDU -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] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2013 08:43 AM, Stephan Richter wrote: Hi everyone, I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot properly ported to Python 3, since it depends heavily on the cmp() way of sorting. I am also not a user of the package and I only tried to port the package for completeness sake. Thoughts? I'm generally in favor of shrinking the ZTK, but just for discussion's sake: emulating 'cmp' for objects which have rich comparison semantics isn't that difficult:: def _faux_cmp(lhs, rhs): return int(rhs lhs) - int(lhs rhs) 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/ iEYEARECAAYFAlEvhpoACgkQ+gerLs4ltQ54KACggufMQUYdhD1Y9pefcP0qvAEE oEMAoLwcOL9/gGtdsIUJ0YlMme85WGhZ =ayRa -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] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2013 10:41 AM, Lennart Regebro wrote: Reading through the code, it seems to use a lot of code to provide quite basic sorting functionality. It feels like it's trying to fill the same role as sorted() does since Python 2.4. The other features (locale-aware sorting, sort different keys using different algorithms / directions) are not easy to emulate using 'sorted()' 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/ iEYEARECAAYFAlEvhtAACgkQ+gerLs4ltQ7PRACbBuZ7YPdTbm0zsqCExZYn/gM0 7cwAoNhy13Nd/Avf0NZ6b+ChqbrfY77E =pITz -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] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2013 01:04 PM, Stephan Richter wrote: On Thursday, February 28, 2013 11:32:26 AM Tres Seaver wrote: Thoughts? I'm generally in favor of shrinking the ZTK, but just for discussion's sake: emulating 'cmp' for objects which have rich comparison semantics isn't that difficult:: def _faux_cmp(lhs, rhs): return int(rhs lhs) - int(lhs rhs) Well, that is the obvious implementation of cmp(), but that's not the point of the package. The package provides a callable class that represents a cmp() function. The problem is that it is not just creating some keys and calls cmp() on it. I could not find out a way to create a single key. The main export of the package is the 'sort' function, which takes a sequence, per-column sort specs (key/attr name, sort function, direction), and optional extra data (e.g., the DTML namespace) and a flag indicating whether to use key or attribute lookup. The 'SortBy' class is really just an implementation detail of that API. I guess the right way to port the package is to implement a sort API. I have ported it to Python 3.2 and 3.3 and released a 4.0.0 version. 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/ iEYEARECAAYFAlEvuFEACgkQ+gerLs4ltQ7+0wCg1gdpKIzx1Q1lvS0xVWAhSRIM wPsAniwipqErV4yMTkRDr5GxBz6GJfzW =6SHn -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] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2013 10:00 PM, Lennart Regebro wrote: On Thu, Feb 28, 2013 at 5:33 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2013 10:41 AM, Lennart Regebro wrote: Reading through the code, it seems to use a lot of code to provide quite basic sorting functionality. It feels like it's trying to fill the same role as sorted() does since Python 2.4. The other features (locale-aware sorting, sort different keys using different algorithms / directions) are not easy to emulate using 'sorted()' Locale aware sorting can be tricky, I'll have to look at that code again. Sorting different keys and directions are trivial with sorted(). I'm not sure what different algorithms mean, with sorted you implement a function that returns a sorting key, that sorting key is then used to sort. It should be possible to sort according to any algorithm that way. Assuming an unsorted list of news stories, how would you use sorted to get them ordered by category (ascending) + publication date (descending)? If you spend more than a minute on it (e.g., trying to come up with a bug-free way to compute negative dates) you've proved my mpoint. :) 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/ iEYEARECAAYFAlEwGqcACgkQ+gerLs4ltQ64PACgoDSWLIhu1EJqTu1zEanfgHlY oxAAoJkzmsOK28Rco13S+06YRyMVhZ8k =T8Or -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] ZTK 2.0 process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2013 11:04 AM, Hanno Schlichting wrote: My goals for a 2.0 release would be (comparing to http://docs.zope.org/zopetoolkit/releases/overview-1.1.html): - Drop support for Python 2.5 (ZTK 1.1 still supports that) +1. - Add support for Python 3.x (either 3.3 or 3.2 and 3.3) I would prefer 3.2 and 3.3. The major hurdle for 3.2-compatibility is unicode literals: I volunteer to do the work if needed to fix that up for the 3.3-ported packages. - Drop all zope.app packages from the KGS (most were deprecated in ZTK 1.1) +sys.maxint - Update to buildout 2 - Update to ZODB 4 +1 to both. 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/ iEYEARECAAYFAlEs7IoACgkQ+gerLs4ltQ5zCACfbHYVhZES9b6BBnj/OKLytaNu MToAnAyA//okvxRZdWrDL5XxgTBA7GSQ =2JJu -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-tests - FAILED: 21, OK: 19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2013 10:46 AM, Stephan Richter wrote: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) To be clear: what is missing is the pure-Python reference implementation of the spacesuit proxies: without having that in place, passing the same tests as the C version, and at 100% statement coverage, I'm not convinced the Py3k port is correct (even though the C version passes all its existing tests under Py3k). Essentially, I rushed the Py3k port in order not to block others working on porting dependents. I have relevant experience in the zope.proxy port that doing the reference implementation actually uncovers bugs in the C implementation. * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) AFAIK, the remaining test failures on Py33 are largely spurious (doctest repr issues, or else are pending the fork to use 'zodbpickle'. Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). Packages which are still bleeding-edge themselves should be OK with pinning non-final releases of their dependencies. 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/ iEYEARECAAYFAlEs+EcACgkQ+gerLs4ltQ5AigCeLY5NgANp+RLFYyzpFUZa0hBM v58AoIy2utc2SMHK2ibjIgMvW5aW5CmP =9em0 -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] SVN: DateTime/trunk/ Moved to GitHub.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/25/2013 01:18 AM, Stephen Richter wrote: Premature. 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/ iEYEARECAAYFAlEraxMACgkQ+gerLs4ltQ4kMwCgrOtFjTc3/ToGcLAmsRnZI1hB 8/0AoIP2T8BEoHEHlu7oKpkkWpJHRwOd =E33A -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-tests - FAILED: 12, OK: 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/24/2013 08:00 PM, Zope tests summarizer wrote:
[2]FAILED Still Failing - zopetoolkit_trunk - Build # 183
https://mail.zope.org/pipermail/zope-tests/2013-February/072774.html
[3]FAILED Still Failing - zopetoolkit_trunk_app - Build # 165
https://mail.zope.org/pipermail/zope-tests/2013-February/072775.html
Both of these show::
Traceback (most recent call last):
File /tmp/tmpkKqMJl, line 11, in module
execfile('/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi/setup.py')
IOError: [Errno 2] No such file or directory:
'/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi/setup.py'
While:
Installing.
Processing develop directory
'/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi'.
[7]FAILED winbot / z3c.form_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072767.html
Stray carriage returns in doctest output.
[8]FAILED winbot / z3c.jsonrpc_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072766.html
FaIluire in doctest exercising proxy:
File c:\eggs\z3c.json-0.5.4-py2.6.egg\z3c\json\proxy.py, line
153, in __request
raise ResponseError(Invalid request id returned)
ResponseError: Invalid request id returned
[9]FAILED winbot / z3c.jsontree_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072768.html
Same as [8].
[10] FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072765.html
Unicode / str mismatches, plus maybe a dict ordering bug in a doctest.
[11] FAILED winbot / zope.app.pagetemplate_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072769.html
Stray carriage returns in doctest output.
[12] FAILED winbot / zope.viewlet_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072796.html
bootstrap failure:
Error: Couldn't open c:\buildslave\zope.viewlet\build\buildout.cfg
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/
iEYEARECAAYFAlEq2OkACgkQ+gerLs4ltQ4fagCfSYPSjZ1r8qXutbytPQrOoilQ
s6wAn2Fo1yKhdS9SU1+gNHGWn9qj54Vp
=8tNC
-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] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2013 10:47 AM, Sebastien Douche wrote: On Mon, Dec 3, 2012 at 10:44 AM, Sebastien Douche sdou...@gmail.com wrote: Hi all, Does anyone (Tres?) can list ZTK packages w/o Python 3 support? What is the right version of ZODB : https://pypi.python.org/pypi/ZODB/4.0.0a4 or https://pypi.python.org/pypi/ZODB3/3.11.0a2 ZODB 3.11.x will never be Py3k-compatible. ZODB 4.0.0a4 is not (yet) Py3k-compatible, but a 4.0.0 final release may be. 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/ iEYEARECAAYFAlEnxXsACgkQ+gerLs4ltQ6AFgCeP6OVEbewypKv3ThyXKx3YaqW C64AoLlDLp57SWDlEEUIoXa9u9pQGbdZ =rOZR -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-tests - FAILED: 11, OK: 15, UNKNOWN: 4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2013 09:48 AM, Marius Gedminas wrote: [5]FAILED Still Failing - zopetoolkit_trunk - Build # 178 https://mail.zope.org/pipermail/zope-tests/2013-February/072600.html Error: Picked: BTrees = 4.0.5 So now zope.annotation requires BTrees, which is not part of the ZTK. Two options: * pin zope.annotation to an older branch that didn't require BTrees * add BTrees and the other exploded-ZODB3-packages to the ZTK, switch ZODB3 from the 3.10 branch to trunk Rather than the ZODB trunk, the ZTK trunk could pull in ZODB 4.0.0a4, which then depends on BTrees, persistent, etc. The alpha status of that release is an indication of more work to be done (porting to PyPy and Py3k, mostly). But the release itself should be usable for testing the ZTK. 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/ iEYEARECAAYFAlEk9HcACgkQ+gerLs4ltQ7a3QCfVfzAcVXIO3iGlWSXVV/fyh0V sMcAoLHrquKlSOR/4nV0w/Ox+6Z+VGhC =+9nT -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-tests - FAILED: 44, OK: 21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2013 03:59 AM, Marius Gedminas wrote: [7]winbot / BTrees_py_265_32 Interesting. This looks to be new. The error:: fatal: remote error: GitHub is offline for maintenance. See http://status.github.com for more info. - -- === 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/ iEYEARECAAYFAlEiWMwACgkQ+gerLs4ltQ4VXACfTu9gbDgS0WQ57vCe4qyZAHcl fYMAoJtxZf2fRok3NLFmLQNqAlkvHweN =R848 -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-tests - FAILED: 44, OK: 21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2013 10:21 AM, Marius Gedminas wrote: On Mon, Feb 18, 2013 at 10:59:20AM +0200, Marius Gedminas wrote: On Mon, Feb 18, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [6]Zope 3.4 Known Good Set / py2.4-64bit-linux No progress here. I disabled emails from this buildbot because who cares about stuff this ancient, right? Dunno about that, but the doctest failure in zope.testing.testrunner might be due to some local configuration: basically, there is coverage info jammed into a test summery:: Total: 405 tests, 0 failures, 0 errors in N.NNN seconds. lines cov% module (path) ... testrunner-ex/sample1/sampletests/test1.py) testrunner-ex/sample1/sampletests/test11.py) testrunner-ex/sample1/sampletests/test111.py) testrunner-ex/sample1/sampletests/test112.py) testrunner-ex/sample1/sampletests/test12.py) testrunner-ex/sample1/sampletests/test121.py) testrunner-ex/sample1/sampletests/test122.py) ... False instead of:: Total: 405 tests, 0 failures, 0 errors in N.NNN seconds. False 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/ iEYEARECAAYFAlEiW9QACgkQ+gerLs4ltQ4NuACgwC/HpbhhVc7E5tJbNKfi0+7T sv4AnAzGijTA5MOe0aRdZ8HnEOE6kXRB =KuKD -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-tests - FAILED: 44, OK: 21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2013 03:59 AM, Marius Gedminas wrote: Who wants to come up with something saner than this? Python doesn't seem to expose a mechanism for asking for the '%p' form from Python: print '%p' % id(object()) Traceback (most recent call last): File stdin, line 1, in module ValueError: unsupported format character 'p' (0x70) at index 1 Stackoverflow[1] suggests as an alternative that we avoid the '%p' format character and use the following (its example uses 'printf'): #include inttypes.h #include stdint.h ... printf(%016 PRIxPTR \n, (uintptr_t)ptr); I prefer your workaround, frankly: I'd rather interoduce the weird code in the tests than in C. [1] http://stackoverflow.com/questions/1255099/whats-the-proper-use-of-printf-to-display-pointers-padded-with-0s 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/ iEYEARECAAYFAlEiYswACgkQ+gerLs4ltQ771wCgqtdB/w7v48CnU7EG0lIn82f/ e34AoINlQRwRLGG10vbzgtmrIganS4vH =IaW7 -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-tests - FAILED: 45, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2013 05:16 AM, Marius Gedminas wrote: Options: - add zope.untrustedpython to the ZTK - switch zope.security to the 3.9 branch I'm leaning towards option 1, but I don't know the procedure for adding something to the ZTK. Help? +1 for adding it. The ZTK is still managed in SVN: svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk You should be able to add it to the three config files used to build / test the ZTK: - ztk.cfg - ztk-sources.cfg - ztk-versions.cfg Incidentally, the changelog on the PyPI page for zope.security has no mention of 3.9.x, but the branch (and a 3.9.0 tag) exists in SVN? What happened there? Just an oversight. The history goes something like: - - I released zope.proxy 4.1.0, breaking BBB for then-current zope.security 3.8.3. which had been made from the trunk (2012-12-19). - - I then made the 3.8 branch, and released 3.8.4, pinning z.proxy 4.1dev (2012-12-21). - - Discovering that 3.8.4 included the trunk version of the proxy.h header, I made the 3.8.5 release, copying in the compatible header (2012-12-20). - - FBO the ZTK trunk, I made the 3.9 release, pinning z.proxy = 4.1.0, and including the compatilbe proxy.h header. We just need to fold in that history, which is present on the 3.8 and 3.9 branches, but not the trunk. I will check that in 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/ iEYEARECAAYFAlEf3esACgkQ+gerLs4ltQ4r4wCdEWKUe0uv3CZKJJZs1H7IU/qC 3bwAn2Eu9Kgh563OxegUPmESoRo8wYJ6 =kcnq -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-tests - FAILED: 41, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2013 02:09 AM, Marius Gedminas wrote: I suggest we add an untrustedpython extra to zope.security that depends on zope.untrustedpython. And a zope.security.untrustedpython package that emits a deprecation warning on import time and does from zope.untrustedpython import *. I agree. I will work out what this needs today and release a 4.0.0a2. 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/ iEYEARECAAYFAlEeSM4ACgkQ+gerLs4ltQ4mXgCfYAoo0SJnVNeIKOkpyLF7CBev OcsAnjRXx1o6rNo3E+whnn/le5hp8H+M =oglV -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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/13/2013 05:02 PM, Tres Seaver wrote: On 02/13/2013 11:04 AM, Tres Seaver wrote: On 02/12/2013 10:47 PM, Stephan Richter wrote: I saw you finished test coverage tonight for zope.security. What is your timeline to do the port to Python 3? Our efforts are blocked until we get zope.security going. We would be willing to take a shot at the port, but you have just done all the hard work writing the tests, so I do not want to steal the momentum from you. Now that the test coverage is in place, I plan to finish the Py3k conversion today, or tomorrow at the latest. The trunk is now Py3k-compatible. I'd like to hold off on a final 4.0.0 release until I can think about adding PyPy support (pure Python reference implementations of the _proxy and _zope_security_checker stuff). We could push a 4.0.0 alpha if you need it installable from PyPI. Done: http://pypi.python.org/pypi/zope.security/4.0.0a1 The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. 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/ iEYEARECAAYFAlEdRcUACgkQ+gerLs4ltQ7zfACfTdED2bc7LizYEcxyno9G9guk tpEAoJ+lUfuRnqHeELRfkTBJOGEkpbW8 =HoJd -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/ZODB] e7d8ca: Checkpoint of Python 3 port. Over 800 of the 897 u...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:53 AM, Marius Gedminas wrote: Curious: was anyone notified by email about the comments I added to the commit? I got an e-mail per comment. - -- === 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/ iEYEARECAAYFAlEdRtUACgkQ+gerLs4ltQ6FYQCcDKlpp1m/ZOoHZroXhqf4nR+B o9AAoJWKbQyGJymMp/a0udpqwZmsCP81 =3D6b -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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:15 PM, Tres Seaver wrote: The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. I put that work on a branch: https://github.com/zopefoundation/zope.security/tree/pure_python_proxy Likely I won't get back to it this week. 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/ iEYEARECAAYFAlEdTB4ACgkQ+gerLs4ltQ6OZQCfVIM/aPRd8BJkRSDEXx7wg4FM inIAnA0jSbOlTBdpi5P1CYtpUg/3dMF/ =4bBx -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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2013 10:47 PM, Stephan Richter wrote: I saw you finished test coverage tonight for zope.security. What is your timeline to do the port to Python 3? Our efforts are blocked until we get zope.security going. We would be willing to take a shot at the port, but you have just done all the hard work writing the tests, so I do not want to steal the momentum from you. Now that the test coverage is in place, I plan to finish the Py3k conversion today, or tomorrow at the latest. 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/ iEYEARECAAYFAlEbuYMACgkQ+gerLs4ltQ4s3wCbBYky/rRSkkTnQPfkq6IJqwpq OQIAniAIFP3aBX/grlHM7wFcSYzknfCg =l8QV -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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/13/2013 11:04 AM, Tres Seaver wrote: On 02/12/2013 10:47 PM, Stephan Richter wrote: I saw you finished test coverage tonight for zope.security. What is your timeline to do the port to Python 3? Our efforts are blocked until we get zope.security going. We would be willing to take a shot at the port, but you have just done all the hard work writing the tests, so I do not want to steal the momentum from you. Now that the test coverage is in place, I plan to finish the Py3k conversion today, or tomorrow at the latest. The trunk is now Py3k-compatible. I'd like to hold off on a final 4.0.0 release until I can think about adding PyPy support (pure Python reference implementations of the _proxy and _zope_security_checker stuff). We could push a 4.0.0 alpha if you need it installable from PyPI. 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/ iEYEARECAAYFAlEcDV0ACgkQ+gerLs4ltQ6WoACgmR0iPfQc2VbYOZ92maSWyior IgAAn2uvQv58q72Gn7ACj7HRR9WM46kL =/yBO -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] 390d12: zope.security.untrustedpython moved to separate pr...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2013 12:23 PM, GitHub wrote: Branch: refs/heads/master Home: https://github.com/zopefoundation/zope.security Commit: 390d1258382d5473388fb6d2fc80f392d4991cf8 https://github.com/zopefoundation/zope.security/commit/390d1258382d5473388fb6d2fc80f392d4991cf8 Author: Andrey Lebedev and...@lebedev.lt Date: 2013-02-12 (Tue, 12 Feb 2013) Changed paths: M CHANGES.rst M buildout.cfg M setup.py R src/zope/security/untrustedpython/__init__.py R src/zope/security/untrustedpython/builtins.py R src/zope/security/untrustedpython/interpreter.py R src/zope/security/untrustedpython/rcompile.py Log Message: --- zope.security.untrustedpython moved to separate project The code was extracted to zope.untrustedpython project to simplify porting zope.security to python-3.x. This change broke the doctest snippets in the Sphinx docs: Document: narr - -- ** File narr.rst, line 571, in default Failed example: from zope.security.untrustedpython.builtins import SafeBuiltins Exception raised: Traceback (most recent call last): File /opt/Python-2.6.8/lib/python2.6/doctest.py, line 1253, in __run compileflags, 1) in test.globs File doctest default[0], line 1, in module from zope.security.untrustedpython.builtins import SafeBuiltins ImportError: No module named untrustedpython.builtins (and many more failures after that) I'm guessing that those document sections (pretty much everything from Safe Builtins to the end of narr.rst) should all be moved to the new project's own Sphinx docs. 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/ iEYEARECAAYFAlEai5kACgkQ+gerLs4ltQ6TrgCgoJfzpZoXDsWpBtYQxUUk6sdr 5AQAnjQ0ayvAnmFrvZK1WpqUZyJk3nsf =1r9K -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] github repositories needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/2013 03:44 PM, Stephan Richter wrote: Hi everyone, In my effort to port packages I would also like to move them to github. I have ported or are in the process of porting the following packages and would like to get Github repositories for them: - z3c.datagenerator - zope.lifecycleevent - zope.filerepresentation - zope.annotation - zope.i18n - zope.container - zope.publisher - zope.traversing - zope.site Note: My goal is to port zope.site this week and Marius is working on zope.pagetemplate. Empty repositories created: the 'Developers' group should have push access. - -- === 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/ iEYEARECAAYFAlEZW08ACgkQ+gerLs4ltQ7t6QCfRC+AcflmpPuYgNytnMkrEX+8 prkAni8LLhVtkNVlnNgSzE1ARk+KZyLf =eT1L -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.security
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/2013 03:36 PM, Stephan Richter wrote: Hi Tres (and everyone else reading along), as you are probably aware, zope.security is a package that blocks a lot of other packages from being ported. I just checked out the coverage on Github and it looks like you are making good progress. The biggest issue I see with zope.security is its dependency on RestrictedPython, because I think that will take a long time to port correctly. However, most of zope.security is very much usable and used without zope.security.untrustedpython. I propose to split zope.security.untrustedpython into a separate package called zope.untrustedpython, so that a port of zope.security to Python 3 can move forward. (Note: I am signing up for the work.) +1 for splitting out the RP dependency. 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/ iEYEARECAAYFAlEZgBwACgkQ+gerLs4ltQ6P0ACfXXfQJvd78p3+4mk+tEDFaA0a usoAoMNLK7YqxrU089DTQAKDq/HoNZ22 =0e3S -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.security
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/2013 09:16 PM, Stephan Richter wrote: On Monday, February 11, 2013 06:34:52 PM Tres Seaver wrote: I propose to split zope.security.untrustedpython into a separate package called zope.untrustedpython, so that a port of zope.security to Python 3 can move forward. (Note: I am signing up for the work.) +1 for splitting out the RP dependency. Okay, if you create a zope.untrustedpython project on Github, I will get to it tomorrow or tonight. 'zope.untrustedpython' repository created. 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/ iEYEARECAAYFAlEZvDsACgkQ+gerLs4ltQ6G2ACg2QA1O903eN8JXtNTR1qoiLkw 5FEAoLQAmAbWaDcCtICusy82eaBYUQcX =uNeM -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] SVN: zope.dottedname/trunk/tox.ini Give up on nose-based coverage, I cannot make it work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/2013 11:11 AM, Marius Gedminas wrote:
Your issue is actually Pip screwing up namespace packages[1], which then
interferes with Nose test discovery. From zope.component's tox.ini::
[testenv:coverage]
basepython =
python2.6
commands =
# The installed version messes up nose's test discovery /
# coverage reporting
# So, we uninstall that from the environment, and then install the
# editable version, before running nosetests.
pip uninstall -y zope.component
python -c import shutil; shutil.copyfile('src/zope/__init__.py',
'{envdir}/lib/python2.6/site-packages/zope/__init__.py')
pip install -e .
nosetests --with-xunit --with-xcoverage
deps =
zope.component
zope.testing
zope.hookable
ZODB3
zope.location
zope.proxy
zope.security
zope.configuration
zope.i18nmessageid
nose
coverage
nosexcover
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/
iEYEARECAAYFAlEP6HsACgkQ+gerLs4ltQ7NogCgrtYwV5zpaU7gH90TsSAWDjuD
TyoAoMORhfXWFirjk+gUIv255OO2SrP5
=nUhN
-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] Git conversion with svn-all-fast-export
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/2013 02:59 PM, Marius Gedminas wrote: Speaking of this, could somebody create a zope.dottedname repo? Thanks. Done. 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/ iEYEARECAAYFAlEQIcEACgkQ+gerLs4ltQ5d9wCgq9HEYwd7BiL1KuuzQCV+Ks2n dgUAni4Eod+a4m5l2IhDDFoUJDRM+bC7 =KzJ+ -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] Announcement: 2013 Zope Foundation Board Elections and General Meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (please forgive the crosspost: we need this announcement to be read as widely as possible). The Zope Foundation board is pleased to announce the regular 2013 general meeting of the foundation will be held on Friday, 22 March 2013, at 15:00 UTC. The meeting will be conducted via IRC at the following channel: irc://irc.freenode.net/#zope-foundation Prior to that meeting, the current board will conduct an elections in which foundation members will select seven (7) board members in accordance with the foundation bylaws[1]. Summary - --- - - Nominations open via the foundat...@zope.org mailing list until Friday, 2013-02-15. - - Voting via e-mail to a closed mailing list, from Wednesday, 2013-02-20 through Friday, 2013-03-08. - - Votes tallied by representatives of the current board, using Meek and Warrent STV method using OpenSTV software. - - General meeting and seating of the new board, Friday, 2013-03-22. Procedure for Elections - --- The procedure for the elections is as follows: - - Foundation members may nominate any member by responding to the board's announcment on the foundat...@zope.org maling list. Nominations will remain open until Friday, 2013-02-15, 23:00 UTC. - - At the close of the nominations period, the board will create a new mailman list, 'zf-elections-2013', and approve all ZF members to post to the list. In order to preserve anonymity of votes, foundation members will not be subscribers to the list; access to the list archives will be restricted to the tellers appointed by the board. - - On Wednesday, 2013-02-20, the Secretary will send an e-mail announcing the opening of the voting period. This email will contain the ballot, with careful instructions about how to rank preferences in the reply. The Reply-to header of this e-mail will be set to the 'zf-elections-2013' list. - - ZF members will vote by replying to that e-mail. Voting will remain open until Friday, 2013-03-08, 23:00 UTC. - - At the close of voting, the board will appoint two of its members as tellers. The tellers will use the list archive to tabulate the members' votes, using the OpenSTV application[2] configured to use the Meek and Warren STV method[3]. The tellers will report the election results, along with the raw tallies, at a special board meeting to be held on Tuesday, 2013-03-20, 15:00 UTC. - - After canvassing the results from the tellers, the board will notify all nominees of the success / failure of their candidacy, thanking them for their willingness to serve. - - At the general meeting, the last item on the agenda will the announcement of the election results, including a vote to seat the board. An online version of this announcement is available at: http://foundation.zope.org/news/2013_election_and_general_meeting References - -- [1] http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf [2] http://stv.sourceforge.net/aboutopenstv [3] http://stv.sourceforge.net/votingmethods/meek 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/ iEYEARECAAYFAlEL6ysACgkQ+gerLs4ltQ5dhACgxeeRpgLSMKjLuW5NLfwTM1Tz A7sAnAphPm/PKiNbJsvRSzpoKB9W66dy =U7sv -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] dtml-try with z-sql
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/01/2013 04:27 AM, murat bilal wrote: I have DTML-Method like below dtml-try dtml-call deleteUser(USERNAME=USERNAME) dtml-except An error occurred. Entry was bNOT/b deleted. /dtml-try deleteUser is Z-SQL method.USERNAME is the argument in Z-SQL method also column name. When i click erase button it succesfully deletes record.But if i enter an invalid username it did not throw any exceptions. This issue is unrelated to DTML / ZSQLMethods. SQL statements like the following:: DELETE FROM some_table WHERE id = 123; don't cause exceptions to be raised for an unknown value like 123; they just affect no rows. If you need an error raised, you need to do something like create a stored procedure on the server which does that. 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/ iEYEARECAAYFAlEL7m8ACgkQ+gerLs4ltQ5uVgCfYRw7x3XAfwsdoFkJCNZm1U3H DKgAoLT358rI08s8GMwanffFV4jT4f8Y =StFb -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-tests - FAILED: 2, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071764.html I'm not terribly certain, but this looks like a timeout / race condition on a test, perhaps due to load on the machine? Failure in test c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt -- File c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt, line 220, in historical_connections.txt Failed example: [c in conns1 for c in conns2] Expected: [False, False, True, True] Got: [False, False, False, True] The text above the failed example seems to expect that the first two connections would have timed out / been garbage collected, but that the second two would be fresh enough to be reused. [2]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071765.html The same failure. I reiterate that somebody who knows / cares about the 'zc.recipe.paster' project needs to step in an fix this failure, or else we need to retire its nightly test run. 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/ iEYEARECAAYFAlEIftQACgkQ+gerLs4ltQ5scgCdESe9ZLgWyKZwYPVxxKzvnPcN diMAoKj/JEfukaFwUO9O9KzcsMo5go+T =9qq4 -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] Bug#692899: zope2.12: [CVE-2012-5485 to 5508] Multiple vectors corrected within 20121106 fix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/27/2013 08:49 AM, Julien Cristau wrote: On Mon, Nov 26, 2012 at 18:53:58 +0900, Arnaud Fontaine wrote: Tres Seaver tsea...@palladion.com writes: * CVE-2012-5505 (zope.traversing: atat.py) http://plone.org/products/plone/security/advisories/20121106/21 That fix is also disputed: hiding the default view from the '@@' name does not actually improve security at all. There is a Launchpad bug where it is being debated (#1079225), but that bug is still in Private Security mode. The correct fix is to change the code of the multi-adapter to barf if published via a URL. Any idea when this patch will be released? Thanks. Is there any news on that issue? I still believe the report is in error: we cannot hide default (unnamed) views simply because an application might register one in error. Any views which wants not to be called via URLs needs to handle that directly: registering a multiadapter for (IThing, None) *is* registering a view. 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/ iEYEARECAAYFAlEFTwsACgkQ+gerLs4ltQ6FVACgmfgoLVb+YLTfJCqHEX4cvd+K ywkAn32iTCbw7oCm5EgC7uI60bJiRm1M =mRXV -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] Bug#692899: zope2.12: [CVE-2012-5485 to 5508] Multiple vectors corrected within 20121106 fix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/27/2013 11:55 AM, David Glick (Plone) wrote: On 1/27/13 6:00 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/27/2013 08:49 AM, Julien Cristau wrote: On Mon, Nov 26, 2012 at 18:53:58 +0900, Arnaud Fontaine wrote: Tres Seaver tsea...@palladion.com writes: * CVE-2012-5505 (zope.traversing: atat.py) http://plone.org/products/plone/security/advisories/20121106/21 That fix is also disputed: hiding the default view from the '@@' name does not actually improve security at all. There is a Launchpad bug where it is being debated (#1079225), but that bug is still in Private Security mode. The correct fix is to change the code of the multi-adapter to barf if published via a URL. Any idea when this patch will be released? Thanks. Is there any news on that issue? I still believe the report is in error: we cannot hide default (unnamed) views simply because an application might register one in error. Any views which wants not to be called via URLs needs to handle that directly: registering a multiadapter for (IThing, None) *is* registering a view. Plone includes the configuration of zope.annotation which registers a multiadapter of (IAnnotations, Interface) that, as far as I can tell, is not intended as a view and can expose information that was meant to be private. Our patch therefore monkey-patched the view traverser in zope.traversing to prevent it from being published. zope.annotation is not configured in Zope 2 out of the box. If you believe that the '(IAnnotation, None)' registration is not supposed to be a view, then the correct place to address this is in 'zope.annotation', not the publisher. E.g.:, the attached patch. Note that the two-argument registration was added by Jacob Holm in r72995 (2007-03-05). CC'ing him to ask if he can recall the justification, or knows what would break if we removed it. At a guess, the motivator is zope.app.preference, which wnats the extra argument passed to its __new__: this is *not* a reason to reguster a multi-adapter. 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/ iEYEARECAAYFAlEFbAEACgkQ+gerLs4ltQ6vSgCff1kX2u+mhrvly+m0uBSg5DD+ nBoAoMVdVCnKzrHwPIleuHhHIHpM7Xkw =e1VT -END PGP SIGNATURE- === modified file 'src/zope/annotation/configure.zcml' --- src/zope/annotation/configure.zcml 2011-02-15 15:46:28 + +++ src/zope/annotation/configure.zcml 2013-01-27 18:00:07 + @@ -8,10 +8,4 @@ factory=.attribute.AttributeAnnotations / - adapter - for=.interfaces.IAttributeAnnotatable * - provides=.interfaces.IAnnotations - factory=.attribute.AttributeAnnotations - / - /configure === modified file 'src/zope/annotation/tests/test_configure.py' --- src/zope/annotation/tests/test_configure.py 2011-02-15 15:46:28 + +++ src/zope/annotation/tests/test_configure.py 2013-01-27 18:01:03 + @@ -36,7 +36,7 @@ zope.configuration.xmlconfig.XMLConfig( 'configure.zcml', zope.annotation)() self.assertEqual(u_count + 2, len(list(gsm.registeredUtilities( -self.assertEqual(a_count + 2, len(list(gsm.registeredAdapters( +self.assertEqual(a_count + 1, len(list(gsm.registeredAdapters( self.assertEqual( s_count, len(list(gsm.registeredSubscriptionAdapters( self.assertEqual(h_count, len(list(gsm.registeredHandlers( ___ 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-tests - FAILED: 2, OK: 21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071673.html [2]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071651.html I can reproduce this failure on Unix, but haven't the slightest idea why: running the buildout inside a doctest can't install the following: 'BTrees=4.0.0dev,4.1dev' which is clearly installable:: $ /opt/Python-2.6.8/bin/virtualenv yyy New python executable in yyy/bin/python Installing setuptoolsdone. Installing pip...done. $ bin/easy_install 'BTrees=4.0.0dev,4.1dev' Searching for BTrees=4.0.0dev,4.1dev Reading http://pypi.python.org/simple/BTrees/ Reading http://packages.python.org/BTrees Best match: BTrees 4.0.5 ... Finished processing dependencies for BTrees=4.0.0dev,4.1dev Can one of the project's maintainers (Michael Howitz, Roger Ineichen, Adam Groszer have made non-trivial checkins) please address the issue? Alternately, can we please drop it from the daily test run, on the grounds that it is not being actively maintained? 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/ iEYEARECAAYFAlECkkkACgkQ+gerLs4ltQ7vOQCgkyKPn527DCNTOo3wgB6JjWF5 Q2AAnR5vkT5GiZav0GIHnt2s4sYmRUwv =q8Ln -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] zc.ssl ca chain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/25/2013 11:22 AM, Senner, Talin wrote: Would someone that has access be able to update zc.ssl and release a new version: http://svn.zope.org/zc.ssl/trunk/src/zc/ssl/certs.pem with a new version of ca root certificates (something say from a latest linux release from /etc/ssl ). The current cert chain is over 5 years old. That package appears to have been maintained last by Zvezdan Petkovic. I have CC'ed his ZC address, although I am not certain he is still at ZC. 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/ iEYEARECAAYFAlECuQEACgkQ+gerLs4ltQ7x/gCeN2sIfcsi1CBLyEboxrejpB8L lq8AoM+/EBHSHeWidy43r3C1QYrc+yZr =UMfd -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-tests - OK: 21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GOAL! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEDWHcACgkQ+gerLs4ltQ7rDACggoKAAlMgvT9epztIGGYjEIlZ L2wAn1U4G7JsuV2W3d7XnIaf64k3F/3Y =786A -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.pagetemplate release wanted [was: Re: zope-tests - FAILED: 1, OK: 21]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/2013 01:29 PM, Maurits van Rees wrote: Op 23-01-13 02:00, Zope tests summarizer schreef: Non-OK results -- [1]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071606.html This should be fixed with a new zope.pagetemplate release. Can anyone do that? PyPI Package Index Owners are: baijum, J1m, ctheune, projekt01, srichter, philikon, benji, ignas, fdrake, chrism, mgedmin, pcardune, ccomb, faassen, chrisw, hathawsh, nadako, hannosch, icemac, tseaver, thefunny42, gary, roymath, kobold, tlotze, agroszer, menesis, davisagli I will make a release. 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/ iEYEARECAAYFAlEAPYYACgkQ+gerLs4ltQ6JNwCcC63+dcQCTaWNozov8wboCP+o 8YAAoJnZnut6pGmc8OigO8nwsgXoZREi =Dy3a -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.pagetemplate release wanted [was: Re: zope-tests - FAILED: 1, OK: 21]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/2013 02:44 PM, Tres Seaver wrote: On 01/23/2013 01:29 PM, Maurits van Rees wrote: Op 23-01-13 02:00, Zope tests summarizer schreef: Non-OK results -- [1]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071606.html This should be fixed with a new zope.pagetemplate release. Can anyone do that? I will make a release. Done: http://pypi.python.org/pypi/zope.pagetemplate/4.0.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.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEAP1sACgkQ+gerLs4ltQ7EcgCfdG5GLYyWp/lPlcVXw+7Lmey+ LAIAn1zavi4hIVCgtKhZ/LsNNgRmHzft =pUjs -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-tests - FAILED: 5, OK: 19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/18/2013 08:58 AM, Maurits van Rees wrote: Op 16-01-13 18:47, Tres Seaver schreef: [3]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071440.html Same error related to the recent zope.pagetemplates changes. This is a test that passes with standard zope.pagetemplates, but fails in combination with Chameleon. It is in a recursion test that has been added in zope.pagetemplate 4.0.0. I have now added a bin/testcompat script in the zope.pagetemplates buildout to test with z3c.pt(compat) plus Chameleon. The expected output for this test is: !-- See https://bugs.launchpad.net/zope.pagetemplate/+bug/732972 -- ul liroot/li li ul lifirst/li /ul /li li ul lisecond/li /ul /li /ul The real output is: !-- See https://bugs.launchpad.net/zope.pagetemplate/+bug/732972 -- ul liroot/li li ul lifirst/li /ul /li li ul lisecond/li /ul /li /ul The difference is that the two inner '/ul' get an extra line before them with a single space character. I have tried a few changes in the test template to see if that would result in the output html being the same with and without Chameleon, but that did not work. Possibly this needs a change not in zope.pagetemplate but in Chameleon or one of the other packages. Or use ElementTree to normalize the XHTML before testing (since the whitespace diffreences are semantically irrelevant). 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/ iEYEARECAAYFAlD5abkACgkQ+gerLs4ltQ4qIACgnPul4E9ztNS5Y3bhXiQRGIa4 fFYAn170Y1Z6b0fe7MQkZKSWfh9ABs/4 =Xn2k -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-tests - FAILED: 5, OK: 19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/15/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 141 https://mail.zope.org/pipermail/zope-tests/2013-January/071443.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 124 https://mail.zope.org/pipermail/zope-tests/2013-January/071442.html These are both failing due to timeouts against svn.zope.org. [3]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071440.html Same error related to the recent zope.pagetemplates changes. [4]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071463.html Same arror with mabe a stale (non-PyPI) index? [5]FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071441.html No information in the failed test output at all 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/ iEYEARECAAYFAlD2560ACgkQ+gerLs4ltQ7m6wCeIVl0UOrGQXIgkbPGjiBu8CjJ fMIAoJmt903KsXsoU7+b8Yh8eZodB9Yu =UlVF -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-tests - FAILED: 16, OK: 16, UNKNOWN: 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED Failure - zopetoolkit_trunk - Build # 139 https://mail.zope.org/pipermail/zope-tests/2013-January/071392.html Timed out checking out 'zope.authentication' from svn.zope.org:: mr.developer: Subversion checkout for 'zope.authentication' failed. mr.developer: svn: Can't read from connection: Connection timed out [2]FAILED Failure - zopetoolkit_trunk_app - Build # 122 https://mail.zope.org/pipermail/zope-tests/2013-January/071393.html Likewise, SVN timeouts. [7]UNKNOWN UNKNOWN : Zope-2.10 Python-2.4.6 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071394.html Appears to be running the tests without first building C extensions (_Acquisition, _zope_proxy_proxy, etc.) [8]UNKNOWN UNKNOWN : Zope-2.11 Python-2.4.6 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071395.html Missing dependency in zope.session? Traceback (most recent call last): File /home/stefan/autotest/temp/python24-zope211/lib/python/zope/session/tests.py, line 30, in ? from zope.session.session import ClientId, Session File /home/stefan/autotest/temp/python24-zope211/lib/python/zope/session/session.py, line 26, in ? import zope.minmax ImportError: No module named minmax [9]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071399.html Bootstrap error: Error: Error downloading extends for URL http://svn.zope.org/repos/main/zopetoolkit/trunk/ztk-versions.cfg: (0, 'got a bad status line') Running ./bin/buildout /bin/sh: ./bin/buildout: No such file or directory [10] FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071385.html [11] FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071382.html [12] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071413.html [13] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071414.html [14] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071384.html [15] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071383.html [16] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071387.html [17] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071380.html [18] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071386.html [19] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071381.html I expect these failures to clear up after my release Saturday of BTrees 4.0.3 (exposing a dummy XXTreeIterator in the pure python implementations of the XXBTree modules). 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/ iEYEARECAAYFAlD0FA8ACgkQ+gerLs4ltQ6rbACeP6ijQbrWxkeVEjNW5Ba4uks7 sEkAoLexgKyzh5JYn5TKVC1nxz+uhnfM =Bi3O -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-tests - FAILED: 6, OK: 18, UNKNOWN: 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/14/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 140 https://mail.zope.org/pipermail/zope-tests/2013-January/071417.html Hmm: mr.developer: Switched 'zope.browserresource' with subversion. mr.developer: Subversion switch of 'zope.browserresource' failed. mr.developer: svn: Can't read from connection: Connection timed out [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 123 https://mail.zope.org/pipermail/zope-tests/2013-January/071418.html Likewise hmm: mr.developer: Switched 'zope.i18n' with subversion. mr.developer: Subversion switch of 'zope.i18n' failed. mr.developer: svn: Can't read from connection: Connection timed out mr.developer: mr.developer: Switched 'zope.principalannotation' with subversion. mr.developer: Subversion switch of 'zope.principalannotation' failed. mr.developer: svn: Can't read from connection: Connection timed out mr.developer: mr.developer: There have been errors, see messages above. [3]UNKNOWN UNKNOWN : Zope-2.10 Python-2.4.6 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071419.html This build looks completely horked: basically every module is non-importable. Blow it away and try again, Stefan? [4]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071415.html Definitely caused by r126016 in zope.pagetemplates/trunk (as released in 4.0.0). Marius, do you have a clue how to fix this one? [5]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071438.html Because this one fails even on Linux trying to install ''BTrees=4.0.0dev,4.1dev', which is perfectly installable for me, I'm guessing it is using an index which needs updating. I don't plan to look farther into the issue: somebody who cares for this package needs to step in: 'adamg' and 'icemac' are the last lucky souls with fingerprints on it. :) [6]FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071439.html [7]FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071416.html These two look like the same kind of failure: a stack smash inside IFBtree index code. I will investigate. 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/ iEYEARECAAYFAlD0124ACgkQ+gerLs4ltQ6mJgCfabLzIlzlU7hgVoKWH8X7b73y abkAoJfDAnpUKLQWMCeEoeZVKhuzDw0z =zDr2 -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-tests - FAILED: 6, OK: 18, UNKNOWN: 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/14/2013 11:13 PM, Tres Seaver wrote: These two look like the same kind of failure: a stack smash inside IFBtree index code. I will investigate. Not a stack smash: the buffer used by Bucket.__repr__ (the C version) was not terminated soon enough (so garbage leaked through). The 'zc.catalog' and 'zope.catalog' tests now pass with the 4.0.5 verstion of BTrees I just released. 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/ iEYEARECAAYFAlD07NwACgkQ+gerLs4ltQ7xGACdEU8tOZp1fOcT7xj1984cJe2x WEMAoL/8ESGYkWjRXXVmIHAYEp2xx+Oe =ze+x -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-tests - FAILED: 18, OK: 19, UNKNOWN: 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/12/2013 08:00 PM, Zope tests summarizer wrote: [1]UNKNOWN UNKNOWN : Zope-2.10 Python-2.4.6 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071351.html I can't reproduce this failure with a fresh checkout of the 2.10 branch. [2]UNKNOWN UNKNOWN : Zope-2.11 Python-2.4.6 : Linux https://mail.zope.org/pipermail/zope-tests/2013-January/071352.html I can't reproduce this failure with a fresh checkout of the 2.11 branch. The rest of the failures are do to a dependeny (in zope.app.security's 'permissions.zcml') on the non-API BTrees iterator classes (the ones used byt the C extensions). I guess I need to merge the branch which would mollify the ZCML :(. 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/ iEYEARECAAYFAlDyFwUACgkQ+gerLs4ltQ7MjACguLiQExWpcRw8IIjoJ6goedNw ivwAn2uZRcHRIToK/oKwwFBLOHeOtTOD =k0oD -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] Status of github migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 06:10 PM, Matthew Wilkes wrote: Tres Seaver wrote: What is needed is not scripts, but eyeballs: we need people who know the various packages and*care* about getting them migrated to github to step up. Softwward which doesn't have a champion willing to do the work should stay behind on SVN. The community as a whole cares about having them all migrated to github. I'm sure this will happen the next time there's a sprint, just like lots of them got migrated (and subsequently deleted) at the zope4 sprint in San Francisco a few years back. The communite as-a-whole demonstrably does *not* care about many of the projects on svn.zope.org. E.g.: https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html We need man-hours, sure, but not champions. Being blocked on working on the code because you're the first one to care about a package and subsequently have to learn how to do the migration is a crazy way of doing things. The foundation agreed to support moving projects to github, but that isn't a blank check. For instance, if there is substantial interest in having the projects pulled in by the current Plone buildout moved, make a list of them, and recruit the folks to step up and help with the migration for them. The effort requires includes doing the conversion, checking the results *by hand*, landing the repository, and fixing anything that breaks once you do (including stuff that breaks in projects you otherwise don't care about). Any project that can't find somebody willing to do that work (that is what I meant by a champion) is better off staying on SVN: we don't do ourselves favors by carrying all the unmaintained baggage of fifteen years worth of development forward, just for purity / completeness / whatever. 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/ iEYEARECAAYFAlDwMPQACgkQ+gerLs4ltQ6HowCgse8NF8ELeMXSLB4USzBJD1mE mRAAnRU1bygjDMqeb3rn/674V/FfuvZY =Erwd -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] Building/Testing persistent package with tox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2013 10:54 AM, Stephan Richter wrote: Hi guys, I have just tried to build/test persistent with tox and it fails with the following error message:: IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt' Complete output from command python setup.py egg_info: Traceback (most recent call last): File string, line 16, in module File /tmp/pip-u7jE1n-build/setup.py, line 29, in module open(os.path.join(here, 'CHANGES.txt')).read()) IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt This is indeed correct, since the ZIP package archive created by tox in ./.tox/dist does not include any txt files. I use the following command to run tox: $ tox -e py27,py32 How do others run tox? Nice catch: this is a side-effect of the move to Git. I just run 'tox' (all environments), but the Python's I use for tox all have setuptools_git installed, so the CHANGES.txt gets included in the temporary sdist. I guess we can ass a MANIFEST.in, since you are certainly not going to be the last person to trip over this issue. /me tries using a Python without setuptools_git: Hmm, the zipefile is built correctly for me. Odd. The two tarballs are identical. 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/ iEYEARECAAYFAlDwOuoACgkQ+gerLs4ltQ7DsACeLIUyz6XocYMSAvdpuY6f9JOe k/4AoJBw/sQA/fLyXVoJZotawPh7I4fg =x2TZ -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] Becoming a zopefoundation member on GitHub
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2013 11:11 AM, Jim Fulton wrote: WRT moving or creating repositories, an unfortunate miss-feature of github is that developers with push access can't also create repositories. (This is one of the reasons that ZC uses bitbucket.) You'll have to ask someone (like me) to do that for you. I don't think we've formalized the process for this. The Foundation's repository committee is Jens plus the folks who have been helping him maintain SVN (Andreas, Jim, ~me). At this point, that group is effectively the only set which can create repositories on Github (the Owners group). Tell one of that group that you want to migrate a project: they will create a new, empty repository for you and grant access. 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/ iEYEARECAAYFAlDwPY8ACgkQ+gerLs4ltQ6A2wCdGSNdH1DGILvPwTPZEAAAxGFJ utUAoJx86L35qyb6TTZTT2oMNZopDadq =xGJH -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] Status of github migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 07:02 AM, Sebastien Douche wrote: On Thu, Jan 10, 2013 at 11:48 AM, Jens Vagelpohl j...@dataflake.org wrote: The GitHub migration happens on an as-needed basis. Don't see the point, why not migrate all active packages (aka the ZTK + ZopeApp)? Because it is a helluva lot of work, which can't be trivially scripted (things can go wrong: each project needs a person who knows it well to review the migrated repo). 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/ iEYEARECAAYFAlDu86MACgkQ+gerLs4ltQ5jMQCfShe7ev+ti+PAS66pXOPVLRZ6 Qy4AoNu3SxntlWgSfMfc7UbkHJ5fQRUo =maE3 -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] How to signal that projects have moved to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 09:15 AM, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in github - Copy above file to root of project. - Make project read only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. I would be happy to add the 'MOVED-TO-GITHUB.txt' files to the SVN projects for the 'zope.*' packages I have already migrated. I need to have the readonly restriction relaxed, first/ 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/ iEYEARECAAYFAlDu8+UACgkQ+gerLs4ltQ78tACg0RqCvxRd269YKdcT+shih/5s y/EAn1aO1PUQamqH4sJaMVgBKH2xK2LP =YRxy -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] How to signal that projects have moved to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 10:42 AM, Patrick Gerken wrote: I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a trunk has been deleted already. Thats not a bug, thats why I run the CI Tool. Would be stupid if I continue to test a trunk not in use. It isn't just CI: people may have projects running from SVN checkouts, which we break without warning (the Plone devs have been notorious for causing such breakage for years). 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/ iEYEARECAAYFAlDu9DUACgkQ+gerLs4ltQ4vpACeP5Tt0m8MkbK/cAOPynlHMerf N4gAnA2ULgxdeGwq81jvlGYuV59NGmdc =FiLH -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-tests - FAILED: 14, OK: 15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/09/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. [3]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071249.html [4]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071250.html [5]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071251.html [6]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071252.html These failures are in tests of now-out-of-date BTrees. We should just remove such tests from the ZODB suite, now that BTrees have their own CI. [11] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071259.html [12] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071258.html [13] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071256.html [14] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071257.html These failures are due to an oddity in the ZCML-based class protections granted by zope.app.security to the (non-API) tree iterators in the C BTrees code. I assume from the fact that these tests fail, that they are running against a BTrees package which does *not* have the C extensions compiled. Those iterator classes are not APIs: they are implementation details of the BTrees C extensions. I speculate somebody added protections for them to zope.app.security to work around an issue with walking space-suit-wrapped BTrees in untrusted code (note that somehow the corresponding TreeSets aren't protected: go figure). I pushed a branch of BTrees which restores the iterators *in name only* in the pure-Python case: https://github.com/zopefoundation/BTrees/tree/expose_tree_iterator Im my branch, trying to actually *use* the XXTreeITerator class in that branch (assuming no C extensions) will raise an exception, but the ZCML class declarations which name the classes should no longer raise. 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/ iEYEARECAAYFAlDu9yAACgkQ+gerLs4ltQ6LGQCdFWY+ol5kZiF7j+MaQlpSo302 4UQAoKOt/TZqWxN9eGMkCZXRJKqx8rhv =8dk5 -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-tests - FAILED: 14, OK: 15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 12:15 PM, Tres Seaver wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. I think I have just fixed these failures by updating the 'ztk-sources.cfg' file to point to the github locations.'bin/develop co '.*' workds, and all tests pass. 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/ iEYEARECAAYFAlDu/FgACgkQ+gerLs4ltQ5BXQCgmtqqTs/zmZTpGe14KOyFgdo4 i34AnA2/mvomHm0IlH2ZnaOLSWo3f8Sm =sPeY -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 )
