Re: [Python-Dev] [New-bugs-announce] [issue7064] Python 2.6.3 / setuptools 0.6c9: extension module builds fail with KeyError
Ned> Due to a change in distutils released with Python 2.6.3, packages Ned> that use setuptools (version 0.6c9, as of this writing), or the Ned> easy_install command, to build C extension modules fail ... ... Ned> Among the packages known to be affected include lxml, Ned> zope-interface, jinja2, and, hence, packages dependent on these Ned> packages (e.g. sphinx, twisted, etc.).
Maybe the Python test suite should include tests with a small number of widely used non-core packages like setuptools. I realize the pybots project exists to tackle this sort of stuff in greater detail. I'm thinking more of a smoke test than a comprehensive test suite covering all external packages. Setuptools is particularly important because so many extension authors use it. If it breaks it implicitly breaks a lot of PyPI packages.
Skip
On Mon, Oct 5, 2009 at 2:50 PM, skip@pobox.com wrote:
Ned> Due to a change in distutils released with Python 2.6.3, packages Ned> that use setuptools (version 0.6c9, as of this writing), or the Ned> easy_install command, to build C extension modules fail ... ... Ned> Among the packages known to be affected include lxml, Ned> zope-interface, jinja2, and, hence, packages dependent on these Ned> packages (e.g. sphinx, twisted, etc.).
Maybe the Python test suite should include tests with a small number of widely used non-core packages like setuptools. I realize the pybots project exists to tackle this sort of stuff in greater detail. I'm thinking more of a smoke test than a comprehensive test suite covering all external packages. Setuptools is particularly important because so many extension authors use it. If it breaks it implicitly breaks a lot of PyPI packages.
I have created 6 months ago such a buildbot that downloads tarballs from the community, and run a few distutils commands on them, and make sure the result is similar in 2.6/2.7. and for "sdist" that the resulting tarball is similar.
It was running over Twisted and Numpy, but has been discontinued because it was on my own server, where it was hard to keep it up (cpu/bandwidth)
If the Snakebite project could host my buildbot (or at least slaves) or if the PSF could pay for a dedicated server for this, we would be able to trigger such warnings, and provide an e-mail service to package maintainers for example.
The build could occur everytime Distutils *or* the project changes.
Skip _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com
Here are three buildbot farms for three different projects that exercise various features of setuptools: build, install, sdist_dsc, bdist_egg, sdist, and various specific requirements that our projects have, such as the "Desert Island Build" in which setuptools is not allowed to download anything from the Internet at build time or else it flunks the test.
http://allmydata.org/buildbot/waterfall http://allmydata.org/buildbot-pycryptopp/waterfall http://allmydata.org/buildbot-zfec/waterfall
I would love it if new versions of setuptools/Distribute would make more of these tests pass on more platforms or at least avoid causing any regressions in these tests on these platforms.
Unfortunately, we can't really deploy new versions of setuptools/Distribute to this buildbot farm in order to re-run all the tests, because the only way that I know of to trigger all the tests is to make a commit to our central darcs repository for Tahoe-LAFS, pycryptopp, or zfec, and I don't want to do that to experiment with new versions of setuptools/Distribute. Does anyone know how to use a buildbot farm like this one to run tests without committing patches to the central repository?
Regards,
Zooko
On 5 Oct, 01:04 pm, ziade.tarek@gmail.com wrote:
On Mon, Oct 5, 2009 at 2:50 PM, skip@pobox.com wrote:
� �Ned> Due to a change in distutils released with Python 2.6.3, packages � �Ned> that use setuptools (version 0.6c9, as of this writing), or the � �Ned> easy_install command, to build C extension modules fail ... � �... � �Ned> Among the packages known to be affected include lxml, � �Ned> zope-interface, jinja2, and, hence, packages dependent on these � �Ned> packages (e.g. sphinx, twisted, etc.).
Maybe the Python test suite should include tests with a small number of widely used non-core packages like setuptools. �I realize the pybots project exists to tackle this sort of stuff in greater detail. �I'm thinking more of a smoke test than a comprehensive test suite covering all external packages. Setuptools is particularly important because so many extension authors use it. �If it breaks it implicitly breaks a lot of PyPI packages.
I have created 6 months ago such a buildbot that downloads tarballs from the community, and run a few distutils commands on them, and make sure the result is similar in 2.6/2.7. and for "sdist" that the resulting tarball is similar.
It was running over Twisted and Numpy, but has been discontinued because it was on my own server, where it was hard to keep it up (cpu/bandwidth)
If the Snakebite project could host my buildbot (or at least slaves) or if the PSF could pay for a dedicated server for this, we would be able to trigger such warnings, and provide an e-mail service to package maintainers for example.
The build could occur everytime Distutils *or* the project changes.
If you want, until Snakebite is up, I can probably provide a slave which can at least do this testing for Twisted and perhaps some other projects.
Jean-Paul
participants (4)
-
exarkun＠twistedmatrix.com -
skip＠pobox.com -
Tarek Ziadé -
Zooko O'Whielacronx