[Zope-dev] version pinning on tags
Hello, I found while trying to get the KGS 3.4.1 together that MISSING versions on tags/previous versions are BAD. The problem is that if you work with the trunk you test the package against (usually) the current versions. If you later get back to a package for a bugfix or whatever, it's a pain to get the tests running again because the dependent package versions shifted. Right now the only chance is to guess versions or KGS's. I'd say we should nail the package versions on (at least) tags. Either to a KGS, or drop a versions.cfg into the package. The recipe buildout.dumppickedversions would be handy. Opinions? -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: All mankind is divided into three classes: those who are immovable, those who are movable; and those who move. - Benjamin Franklin ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 10 OK, 6 Failed
Summary of messages to the zope-tests list. Period Wed Apr 28 12:00:00 2010 UTC to Thu Apr 29 12:00:00 2010 UTC. There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 670 projects From: ct at gocept.com Date: Wed Apr 28 21:17:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014161.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Thu Apr 29 00:22:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014175.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Thu Apr 29 00:46:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014176.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 28 21:29:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014162.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 28 21:31:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014163.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 28 21:33:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014164.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 28 21:35:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014165.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 28 21:37:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014166.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 28 21:39:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014167.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Wed Apr 28 22:00:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014168.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Wed Apr 28 22:00:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014169.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Wed Apr 28 22:00:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014170.html Subject: OK : BlueBream template / Python2.7b1 32bit linux From: ccomb at free.fr Date: Wed Apr 28 22:00:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014171.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] version pinning on tags
On Thursday 29 April 2010, Adam GROSZER wrote: I'd say we should nail the package versions on (at least) tags. Either to a KGS, or drop a versions.cfg into the package. The recipe buildout.dumppickedversions would be handy. +1 to use a KGS. ZTK or BB depending on what the dependencies are. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] windows binaries
On Wednesday 28 April 2010, Adam GROSZER wrote: How do you used to build binaries for windowze? I mean which compilers do you use? mingw32? MS? Ohhh and don't forget win64 ;-) and various python version, like from 2.4 up to 3.1. I did a few releases just using mingw32. I think it is the best we can do for now that scales. As for Python versions, you simply have to installthem all and go through the dance. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] version pinning on tags
On Thu, Apr 29, 2010 at 6:31 PM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Thursday 29 April 2010, Adam GROSZER wrote: I'd say we should nail the package versions on (at least) tags. Either to a KGS, or drop a versions.cfg into the package. The recipe buildout.dumppickedversions would be handy. +1 to use a KGS. ZTK or BB depending on what the dependencies are. Since normally we don't pin versions in trunk, I guess we need to do the pinning in maintenance branches. Otherwise we can keep the version pinning in trunk, but comment the versions option. Then, just before going for release, uncomment it. This will become one more step in creating releases: http://docs.zope.org/zopetoolkit/process/releasing-software.html Regards, Baiju M ___ 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] windows binaries
On Thu, Apr 29, 2010 at 6:36 PM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Wednesday 28 April 2010, Adam GROSZER wrote: How do you used to build binaries for windowze? I mean which compilers do you use? mingw32? MS? Ohhh and don't forget win64 ;-) and various python version, like from 2.4 up to 3.1. I did a few releases just using mingw32. I think it is the best we can do for now that scales. As for Python versions, you simply have to installthem all and go through the dance. Does mingw32 works for 64 bit also ? Regards, Baiju M ___ 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] windows binaries
On Thursday 29 April 2010, Baiju M wrote: I did a few releases just using mingw32. I think it is the best we can do for now that scales. As for Python versions, you simply have to installthem all and go through the dance. Does mingw32 works for 64 bit also ? If you can isntall it on 64bit, it should be able to compile to it as well. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] version pinning on tags
On Thursday 29 April 2010, Baiju M wrote: +1 to use a KGS. ZTK or BB depending on what the dependencies are. Since normally we don't pin versions in trunk, I guess we need to do the pinning in maintenance branches. Otherwise we can keep the version pinning in trunk, but comment the versions option. Then, just before going for release, uncomment it. This will become one more step in creating releases: http://docs.zope.org/zopetoolkit/process/releasing-software.html Why not leave it always pinned? This way the pinning gets transferred to the branch/tag automatically. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 6 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html Christophe, These failures appear to be due to a merge conflict in your local ZTK checkout. E.g., from [1]: An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1659, in main user_defaults, windows_restart, command) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 182, in __init__ data['buildout'].copy(), override)) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1333, in _open eresult = _open(base, extends.pop(0), seen, dl_options, override) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1313, in _open parser.readfp(fp) File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 305, in readfp self._read(fp, filename) File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 510, in _read raise e ParsingError: File contains parsing errors: /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg [line 206]: ' .mine\n' [line 278]: '===\n' [line 350]: ' .r111557\n' Seems like you had local, uncommitted changes there, which kind of hurts our ability to reproduce failures elsewhere. [1]http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.4%20Linux%2032bit/builds/61/steps/bootstrap/logs/stdio Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZkPoACgkQ+gerLs4ltQ5GPACfV0/JsnOJj8t/axiii8OcJ1Hv yusAoILNm4Y1oYa9UTJ2Yy2s9xYWdxyt =xNdK -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 pinning on tags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Thursday 29 April 2010, Baiju M wrote: +1 to use a KGS. ZTK or BB depending on what the dependencies are. Since normally we don't pin versions in trunk, I guess we need to do the pinning in maintenance branches. Otherwise we can keep the version pinning in trunk, but comment the versions option. Then, just before going for release, uncomment it. This will become one more step in creating releases: http://docs.zope.org/zopetoolkit/process/releasing-software.html Why not leave it always pinned? This way the pinning gets transferred to the branch/tag automatically. - -1. Trunk development should not be hindered by the need to maintain a KGS of some sort. Testing the trunk against a given KGS should be a separate step from testing against current releases. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZki8ACgkQ+gerLs4ltQ5t8gCeMJruyrlLi4ugf0wV2hYq0m0V NdIAoNTugaI4iTHHfI0QWNiJkUBw6ejf =ArEb -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 pinning on tags
Hello Tres, Thursday, April 29, 2010, 4:05:36 PM, you wrote: TS Stephan Richter wrote: On Thursday 29 April 2010, Baiju M wrote: +1 to use a KGS. ZTK or BB depending on what the dependencies are. Since normally we don't pin versions in trunk, I guess we need to do the pinning in maintenance branches. Otherwise we can keep the version pinning in trunk, but comment the versions option. Then, just before going for release, uncomment it. This will become one more step in creating releases: http://docs.zope.org/zopetoolkit/process/releasing-software.html Why not leave it always pinned? This way the pinning gets transferred to the branch/tag automatically. TS - -1. Trunk development should not be hindered by the need to maintain a TS KGS of some sort. Testing the trunk against a given KGS should be a TS separate step from testing against current releases. You could extends= some sort of KGS, then override some versions locally. It's just crazy that you buildout friday, test, all tests pass. You buildout monday, test, failures... because some versions moved. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: In Dr. Johnson's famous dictionary, patriotism is defined as the last resort of the scoundrel. With all due respect to an enlightened but inferior lexicographer I beg to submit that it is the first. - Ambrose Bierce ___ 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] I would like to have some releases
I would like to have the following packages released, or the permissions to release them myself. This is all in preparation for Python 3 support. zope.interface zope.events zope.exceptions zope.testing zc.recipe.testrunner The releases of zope.interface, zope.events and zope.exceptions introduce Python 3 compatibility. The release of zope.testing deprecates zope.testing.testrunner for zope.testrunner (just released). zc.recipe.testrunner uses zope.testrunner instead of zope.testing.testrunner. -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64 ___ 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: 10 OK, 6 Failed
Tres Seaver a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Apr 28 23:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html Christophe, These failures appear to be due to a merge conflict in your local ZTK checkout. E.g., from [1]: An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1659, in main user_defaults, windows_restart, command) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 182, in __init__ data['buildout'].copy(), override)) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1333, in _open eresult = _open(base, extends.pop(0), seen, dl_options, override) File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 1313, in _open parser.readfp(fp) File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 305, in readfp self._read(fp, filename) File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 510, in _read raise e ParsingError: File contains parsing errors: /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg [line 206]: ' .mine\n' [line 278]: '===\n' [line 350]: ' .r111557\n' Seems like you had local, uncommitted changes there, which kind of hurts our ability to reproduce failures elsewhere. Ok there is something wrong, I'll clean eveything Before the buildout, I'm doing a sed -i s/svn+ssh/svn/ ztk.cfg zopeapp.cfg because the buildbot is not supposed to have a ssh key. Then I'm doing a svn revert of these two files. But if the buildout fails, the revert is not done. Is there another way to disable ssh? [1]http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.4%20Linux%2032bit/builds/61/steps/bootstrap/logs/stdio Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZkPoACgkQ+gerLs4ltQ5GPACfV0/JsnOJj8t/axiii8OcJ1Hv yusAoILNm4Y1oYa9UTJ2Yy2s9xYWdxyt =xNdK -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 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] windows binaries
Hello Stephan, Thursday, April 29, 2010, 3:45:13 PM, you wrote: SR On Thursday 29 April 2010, Baiju M wrote: I did a few releases just using mingw32. I think it is the best we can do for now that scales. As for Python versions, you simply have to installthem all and go through the dance. Does mingw32 works for 64 bit also ? SR If you can isntall it on 64bit, it should be able to compile to it as well. I guess you can install, but it ought to compile still to 32bit. Windoze is a bit crazy on 64bit, as usual. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: You can't expect a person to see eye to eye with you when you're looking down on him. - Bits Pieces ___ 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 pinning on tags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: Hello Tres, Thursday, April 29, 2010, 4:05:36 PM, you wrote: TS Stephan Richter wrote: On Thursday 29 April 2010, Baiju M wrote: +1 to use a KGS. ZTK or BB depending on what the dependencies are. Since normally we don't pin versions in trunk, I guess we need to do the pinning in maintenance branches. Otherwise we can keep the version pinning in trunk, but comment the versions option. Then, just before going for release, uncomment it. This will become one more step in creating releases: http://docs.zope.org/zopetoolkit/process/releasing-software.html Why not leave it always pinned? This way the pinning gets transferred to the branch/tag automatically. TS - -1. Trunk development should not be hindered by the need to maintain a TS KGS of some sort. Testing the trunk against a given KGS should be a TS separate step from testing against current releases. You could extends= some sort of KGS, then override some versions locally. It's just crazy that you buildout friday, test, all tests pass. You buildout monday, test, failures... because some versions moved. If the develpoers who work on trunk don't live with that problem, how can they expect downstream folks (e.g., real users or KGS maintainers) to figure it out? The workflow I am proposing is that when the nightly tests begin to break due to a dependeny, the developer updates the setup.py (*NOT* the buildout.cfg) to pin minimum or maximum versions of dependencies. Later, the developer might relax or adjust those pins after tweaking the package itself. Prior to release, the developer double-checks those pins. Deferring the pain by testing only against a KGS just means that you lose the information about which changes caused the breakage at the time they happen. When the time comes to update the KGS itself, weeks or months after the fact, the unfortunate KGS maintainer hs no idea what changed or how to fix 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZsJEACgkQ+gerLs4ltQ4SrACgwyzQHz5fHw4odVfX4HPgM6lw IlsAni/AjNuMyRKwLbWSMFcsXB2nW6pi =xhT8 -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] I would like to have some releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Lennart Regebro wrote: I would like to have the following packages released, or the permissions to release them myself. This is all in preparation for Python 3 support. zope.interface zope.events zope.exceptions zope.testing zc.recipe.testrunner The releases of zope.interface, zope.events and zope.exceptions introduce Python 3 compatibility. The release of zope.testing deprecates zope.testing.testrunner for zope.testrunner (just released). zc.recipe.testrunner uses zope.testrunner instead of zope.testing.testrunner. What is your PyPI ID? Never mind, I figured it out. You are now blessed for those packages (note that it is 'zope.event' and not 'zope.events'). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZuSgACgkQ+gerLs4ltQ7ehwCfWACYqXvFin0C2Ybdh4i7pimZ G2AAn0tv3iT9Je80H603EPhS6cOi+F4E =XmhO -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] Another possible zope.testing deprecation...
There is a zope.testing.exceptions module. It contains only one exception: DocTestFailureException, which is used by the testrunner, and as far as I can tell, only the testrunner. So we should probably move that one over to zope.testrunner as well. Which means deprecating it in zope.testing, of course. Anyone see any problems with this? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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] Another possible zope.testing deprecation...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro wrote: There is a zope.testing.exceptions module. It contains only one exception: DocTestFailureException, which is used by the testrunner, and as far as I can tell, only the testrunner. So we should probably move that one over to zope.testrunner as well. Which means deprecating it in zope.testing, of course. Anyone see any problems with this? +1. Does zope.testing depend on zope.testrunner already? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZ5C8ACgkQ+gerLs4ltQ7RzgCgzRC7IqJWfQ4Hp97Syjxeh63q Z7UAn2OSHugS9hZh4XuopJyMSUwDN4VC =waNh -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] I would like to have some releases
OK, I started carefully with zope.interface 3.6.0. :) Source only so far. I have a Windows machine, and I could make Windows releases as well, I guess. Is there any docs on what's needed for that? I haven't built python extensions on Windows since 2004. :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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] I would like to have some releases
On Thu, Apr 29, 2010 at 10:00 PM, Lennart Regebro rege...@gmail.com wrote: OK, I started carefully with zope.interface 3.6.0. :) Source only so far. I have a Windows machine, and I could make Windows releases as well, I guess. Is there any docs on what's needed for that? I haven't built python extensions on Windows since 2004. :) I'll do the Python 2.6 (32-bit + 64-bit) releases tomorrow. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] I would like to have some releases
On Thu, Apr 29, 2010 at 22:03, Hanno Schlichting ha...@hannosch.eu wrote: On Thu, Apr 29, 2010 at 10:00 PM, Lennart Regebro rege...@gmail.com wrote: OK, I started carefully with zope.interface 3.6.0. :) Source only so far. I have a Windows machine, and I could make Windows releases as well, I guess. Is there any docs on what's needed for that? I haven't built python extensions on Windows since 2004. :) I'll do the Python 2.6 (32-bit + 64-bit) releases tomorrow. Great! I don't have 64 bit system, forgot about that. :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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] Another possible zope.testing deprecation...
On Thu, Apr 29, 2010 at 21:55, Tres Seaver tsea...@palladion.com wrote: +1. Does zope.testing depend on zope.testrunner already? No, and with this zope.testrunner doesn't have to depend on zope.testing either, except for running the tests. Freedom baby yeah! :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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 )
