zope.testing / zope.testrunner path forward:
I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3. zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.) The questions are (some have been discussed before, but I don't remember the outcome): 1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long). 2. Should I release the testrunner-free version before I port to Python 3, or should we do both at once?Doing both at once of course risks more problems than one at a time. On the other hand we might want all changes at once to lessen annoyance. 3. It should be zope.testing 4.0.0, right? -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python3porting.com/ +33 661 58 14 64
On Tue, Jul 20, 2010 at 05:32:39PM +0100, Lennart Regebro wrote:
I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3.
I, for one, am extremely grateful that someone (not me, that is) is working on Python 3 compatibility!
zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.)
The questions are (some have been discussed before, but I don't remember the outcome):
1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long).
*shrug*
2. Should I release the testrunner-free version before I port to Python 3, or should we do both at once?Doing both at once of course risks more problems than one at a time. On the other hand we might want all changes at once to lessen annoyance.
I'm for two separate releases. "Release early, release often".
3. It should be zope.testing 4.0.0, right?
and 3.10.0 as the testrunner-less-but-not-yet-py3k-compatible release. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas <marius@gedmin.as> wrote:
I'm for two separate releases. "Release early, release often".
Oh, that's not a problem. svn://svn.zope.org/repos/main/zope.testing/branches/regebro-400 Is testrunner free and runs on Python 3 already. It's purely a question of if we want both changes at once or not. :-) -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64
On 07/21/2010 06:40 AM, Lennart Regebro wrote:
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas<marius@gedmin.as> wrote:
I'm for two separate releases. "Release early, release often".
Oh, that's not a problem. svn://svn.zope.org/repos/main/zope.testing/branches/regebro-400 Is testrunner free and runs on Python 3 already. It's purely a question of if we want both changes at once or not. :-)
I myself prefer having more releases. I like Marius' idea: 3.10 would be good for removing the test runner then 4.0 can be Py3 compatibility. Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Wed, Jul 21, 2010 at 06:28, Christian Theune <ct@gocept.com> wrote:
I myself prefer having more releases. I like Marius' idea: 3.10 would be good for removing the test runner then 4.0 can be Py3 compatibility.
OK, I'll merge and release 3.10 today or tomorrow or so. -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas <marius@gedmin.as> wrote:
1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long).
*shrug*
Nobody said "YES!" and since it actually requires that zope.testing depends on zope.testrunner to be pracically useful, I think we'll skip it. -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64
On Wednesday, July 21, 2010, Lennart Regebro wrote:
Nobody said "YES!" and since it actually requires that zope.testing depends on zope.testrunner to be pracically useful, I think we'll skip it.
I think nobody cares because everyone uses the test runner recipe. As long as that recipe works, we are good. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
On Tue, Jul 20, 2010 at 12:32 PM, Lennart Regebro <regebro@gmail.com> wrote:
I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3. zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.)
The questions are (some have been discussed before, but I don't remember the outcome):
My opinions:
1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long).
No.
2. Should I release the testrunner-free version before I port to Python 3, or should we do both at once?Doing both at once of course risks more problems than one at a time. On the other hand we might want all changes at once to lessen annoyance.
Do whatever is easiest for you. One option would be to release as eggs for Python 3 only. That way, you shouldn't be affecting Python 2 users.
3. It should be zope.testing 4.0.0, right?
Yes Jim -- Jim Fulton
On Wed, Jul 21, 2010 at 15:06, Jim Fulton <jim@zope.com> wrote:
Do whatever is easiest for you. One option would be to release as eggs for Python 3 only. That way, you shouldn't be affecting Python 2 users.
I've released 3.10.0 now, and will let that simmer a while. I'm on Europython so please mail me if something breaks so I see it. 4.0.0 is ready, but I'll wait with releasing it for a week at least, I only need it to work on my porting of zc.buildout, and I don't need it uploaded to PyPI. :-) -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64
On Tue, Jul 20, 2010 at 5:32 PM, Lennart Regebro <regebro@gmail.com> wrote:
I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3. zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.)
Hi Lennart, Just to be clear, is zope.testing 4.0.0 intended to work with Python 2? I'll try to get around to trying 3.10.0 with Launchpad rsn. jml
participants (6)
-
Christian Theune -
Jim Fulton -
Jonathan Lange -
Lennart Regebro -
Marius Gedminas -
Stephan Richter