Version Numbering for Ported Packages
Hi everyone, Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres wanted 4.0.0 to also have PyPy support, so he only did an alpha release to unblock the porting effort. Today, I finished the PyPy support and he released 4.0.0b1. * ZODB: We currently do not have a release for a ported ZODB. For any package requiring the ZODB directly or indirectly, we added a snapshot sdist of the py3 branch into the package to demonstrate the tests passing. (See the zodb- dev mailing list for the current status.) Of course, the alpha releases are really stable, all the tests pass under Python 2.6 and 2.7. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
-----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 tseaver@palladion.com Palladion Software "Excellence by Design" http://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-----
On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote:
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?
I have asked Adam to create lxml 3.1 binary eggs for Windows. He is waiting for someone to give him the Rackspace credentials, so he can backup the Windows box before installed the latest MSVC version. After that, at least half of the failures should be dealt with.
Also, is somebody running / reporting tests via Travis? Where are those results going?
They should be running for all packages. I have turned off any notifications pending an agreement of where we want the reports to go. The easiest thing right now would be a Wiki page that shows the status icon for each package. Note: I think most packages pass fine under Travis, but some are failing for some obscure reasons. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
On Tue, Mar 12, 2013 at 08:35:46AM -0400, Stephan Richter wrote:
On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote:
Also, is somebody running / reporting tests via Travis? Where are those results going?
They should be running for all packages. I have turned off any notifications pending an agreement of where we want the reports to go. The easiest thing right now would be a Wiki page that shows the status icon for each package.
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. Packages without a .travis.yml are treated as Ruby packages, and, obviously, always fail.
Note: I think most packages pass fine under Travis, but some are failing for some obscure reasons.
An overview would be good. I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The image URLs are trivial to generate, assuming Travis knows about every ZF repo on Github: https://api.travis-ci.org/zopefoundation/${reponame}.png?branch=master Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Tuesday, March 12, 2013 04:41:23 PM Marius Gedminas wrote:
Note: I think most packages pass fine under Travis, but some are failing for some obscure reasons.
An overview would be good.
I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The image URLs are trivial to generate, assuming Travis knows about every ZF repo on Github:
https://api.travis-ci.org/zopefoundation/${reponame}.png?branch=master
I did another overview script here: https://github.com/zopefoundation/zope.winbot/blob/master/README.rst It lists all packages that winbot cares about. As we are adding Python versions to winbot, we can easily extend that table. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/12/2013 10:41 AM, Marius Gedminas 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. 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). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFAm74ACgkQ+gerLs4ltQ4VDwCgqOfOLNPy+XhTT8r7ohMFp5xj 4zAAnioeumTxXt6GPaBotKlvu0sN++4+ =lZbN -----END PGP SIGNATURE-----
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. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
-----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 tseaver@palladion.com Palladion Software "Excellence by Design" http://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-----
On Wednesday, March 13, 2013 12:03:44 PM Tres Seaver wrote:
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.
The rough split is like that: - 100+ packages ported to Python 3 (mostly ZTK) - 30+ packages converted for Zope 2 - 25+ packages converted for grok - 50 packages converted for wineggbuilder We have not converted anything without purpose and just because we could. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
participants (3)
-
Marius Gedminas -
Stephan Richter -
Tres Seaver