Mailman 3 July 2013 - Distutils-SIG

beginner ticket for code base modernization of setuptools
by Jason R. Coombs July 13, 2013

July 13, 2013

I've created the following ticket for Setuptools: https://bitbucket.org/pypa/setuptools/issue/35/code-base-modernization I'm inviting junior developers or students or other less experienced enthusiasts who are interested in learning more about the inner workings of Setuptools to assist in a code modernization effort to bring Setuptools more in line with the expectations of modern Python developers. If this effort might interest you, please follow the link for more details. Regards, Jason

1 0

PEP 439 and pip bootstrap updated
by Richard Jones July 13, 2013

July 13, 2013

[firstly, my apologies for posting the announcement yesterday of the pip bootstrap implementation and PEP updates to the pypa-dev list instead of distutils-sig... I blame PyCon AU exhaustion :-)] Firstly, I've just made some additional changes to PEP 439 to include: - installing virtualenv as well (so now pip, setuptools and virtualenv are installed) - mention the possibility of inclusion in a future Python 2.7 release - clarify the SSL certificate situation The bootstrap code has also been updated to: - not run the full pip command if it's "pip3 install setuptools" or either of the other two packages it has just installed (thus preventing a possibly confusing message to the user) - also install virtualenv The intention is that the pip, setuptools and actually all Python projects will promote a single bootstrap process: "pip3 install setuptools" or "pip3 install Django" And then there's instructions for getting "pip" if it's not installed. Exact wording etc. to be determined :-) The original message I sent to pypa-dev yesterday is below: The bootstrap that I wrote at the PyCon AU sprints to implement PEP 439 has been added to pypa on bitbucket: https://bitbucket.org/pypa/bootstrap I've also updated the PEP with the following changes: - mention current plans for HTTPS cert verification in Python 3.4+ (sans PEP reference for now) - remove setuptools note; setuptools will now be installed - mention bootstrapping target (user vs. system) and command-line options - mention python 2.6+ bootstrap possibility - remove consideration of support for unnecessary installation options (beyond -i/--index-url) - mention having pip default to --user when itself installed in ~/.local What the last item alludes to is the idea that it'd be nice if pip installed in ~/.local would default to installing packages also in ~/.local as though the --user switch had been provided. Otherwise the user needs to remember it every time they install a package. Note that the bootstrapping uses two different flags to control where the pip implementation is installed: --bootstrap and --bootstrap-system (these were chosen to encourage user installs). It would be ideal if pip could support those flags, as the pip3 command currently must remove them before invoking pip main. Once we're happy with the shape of pip3 we can fork it to Python 2 and use it as the canonical bootstrap script for installing pip and setuptools. I think we should also consider installing virtualenv in Python 2... Happy to clarify where needed and code review is welcome. It's been a looong four days here :-) Richard

14 81

Issues with Buildout 2.2.0 and a few other questions
by Nathaniel Manista July 12, 2013

July 12, 2013

Hey Buildout Folks- I'm the lead of the Melange project <http://code.google.com/p/soc/> and we've hit two issues with the recent Buildout release. The first is the setuptools version problem described here<http://mail.python.org/pipermail/distutils-sig/2013-July/021447.html>, and the second is the node problem described here<https://github.com/gawel/gp.recipe.node/issues/12> . I see that a package upgrade is the recommended solution to the first problem, but that's not necessarily easy in our case as we've got a mix of corporate machines and academic machines and otherwise managed platforms - is there anything like a list of supported platforms for Buildout 2.2.0? Is Buildout fully supported on Ubuntu 12.04 (the most recent long-term support release of Ubuntu)? Are there known and unsupported incompatibilities on Ubuntu 12.04? Does Buildout maintain a list of supported platforms and configurations? Is the Buildout team aware of the second (node) issue? In looking for my own answers to these questions, I came across some issues on the buildout.org site. This link<http://www.buildout.org/en/latest/_static/img/plone_logo.png>on the front page <http://buildout.org> appears broken, and the latest documentation appears to describe Buildout 1.2.1<http://www.buildout.org/en/latest/install.html>(with out-of-date references such as "wget http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py"). What's going on there? Thanks much, -Nathaniel

1 0

Python packaging + conditional use of C library shipped with the package
by Laurent Gautier July 8, 2013

July 8, 2013

Hi, I would like to make a package that is able to use a system's given C-library if found, or compile its own version shipped with the package. This is bringing up two questions: - Is there a distutils/distribute facility to help test for the presence (and version) of a C library, or do I have to roll my own system ? - When having the source for a C library shipping with a package, is there a way to get distutils/distribute compile it, and get it seen by Python at runtime (so I can just use ctypes, or cffi, and even C extensions in other Python package see the headers and compiled libraries) ? Best, Laurent PS: I have noticed that pyzmq seems to be doing a lot of that, but they also appear to have a relatively big set of custom code do so (setup.py is already a little longer than most install scripts, to which a complete package 'buildutils' should be added)... this makes me anticipate that the answer to my two questions will be "no" ( :/ ) but I'd like a confirmation from the experts.

3 3

bandersnatch 1.0.2: CDN compatibility for mirrors
by Christian Theune July 8, 2013

July 8, 2013

Hi, over the last weeks I worked with Donald to get mirrors working consistently again. I updated the bandersnatch mirror client and the 1.0.2 release has been running on my mirror (f.pypi.python.org) for a few days correctly. If you're running a mirror, please get it and report any further errors you should encounter to the bitbucket issue page: https://bitbucket.org/ctheune/bandersnatch/issues Cheers, Christian Small caveat, nothing big: the statistics that are generated by pypi-mirrors.org show a reduced number of packages available on my mirror, however, that is due to the fact that the master reports a number that includes all packages even without releases. The master serves 404s for their simple pages. Bandersnatch, thus, does not keep their directories. To support the CDN I have to generate the big simple index page myself. The only reliable way to do this is to list all simple pages I actually have. As packages without releases don't have simple pages -> back to square one.

2 2

Setuptools 0.8 and Distribute 0.7.3 (legacy wrapper) now released
by Jason R. Coombs July 8, 2013

July 8, 2013

The PyPA is excited to announce the public release of Setuptools 0.8. This release of setuptools provides no additional functionality over Setuptools 0.7.x except that it no longer requires 2to3 to build/install on Python 3. What this means for packaging is that tools like pip and virtualenv can now invoke setuptools directly on all supported Python versions (currently 2.4+). This build enables more natural upgrades and helps address many of the bugs that the 2to3 conversion process triggered. Additionally, Distribute 0.7.3 has also been released to PyPI. Distribute 0.7 was designed to ease the upgrade process from Distribute 0.6.x to Setuptools 0.7. This new version, 0.7.3, is a re-release of the legacy wrapper 0.7, but additionally bundles the Setuptools 0.8 code for the purposes of bootstrapping the upgrade. This version specifically eases upgrades on systems running older systems. Now, one can readily upgrade any environment with Distribute 0.6 by simply upgrading (using pip or easy_install) to Distribute 0.7.3, which will replace the 'distribute' package with an empty shell leaving setuptools >= 0.7 (probably 0.8) installed. Enjoy, and please report any issues with either of these packages at the Setuptools project page (https://bitbucket.org/pypa/setuptools).

3 2

[issue153] Jython - easy_install -- ssl_support.py: module has no attribute 'CERT_REQUIRED'
by Tom Brennan July 7, 2013

July 7, 2013

New submission from Tom Brennan: Can't install anything with easy_install or pip. Happens in at least v.0.8 and 0.7.8. (stack trace attached is from 0.7.8) ---------- files: easy_install_stack_trace.txt messages: 729 nosy: tjb1982 priority: bug status: unread title: Jython - easy_install -- ssl_support.py: module has no attribute 'CERT_REQUIRED' Added file: http://bugs.python.org/setuptools/file93/easy_install_stack_trace.txt _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue153> _______________________________________________

2 1

[issue152] setuptools breaks with from __future__ import unicode_literals in setup.py
by mbogosian July 6, 2013

July 6, 2013

New submission from mbogosian: unicode_literals break a bunch of stuff in setuptools. Considering they may become the default at some point, this should be fixed...? I do not know if this is related to issue 78. To reproduce, run the attached setup.py (output below). Comment out the unicode_literals line in setup.py and try it again (everything should work). % DISTUTILS_DEBUG=t python -c 'import setuptools ; print setuptools.__version__' 0.8 % unzip -d foo_test.zip ; cd foo_test ... % DISTUTILS_DEBUG=t python setup.py build options (after parsing config files): options (after parsing command line): option dict for 'aliases' command: {} option dict for 'build' command: {} option dict for 'nosetests' command: {'all_modules': ('setup.cfg', '1'), 'cover_package': ('setup.cfg', 'foo'), 'detailed_errors': ('setup.cfg', '1'), 'verbosity': ('setup.cfg', '2'), 'with_coverage': ('setup.cfg', '1'), 'with_doctest': ('setup.cfg', '1')} running build Distribution.get_command_obj(): creating 'build' command object running build_py Distribution.get_command_obj(): creating 'build_py' command object Traceback (most recent call last): File "setup.py", line 58, in <module> setuptools.setup(**_SETUP_ARGS) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build.py", line 127, in run self.run_command(cmd_name) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/setuptools/command/build_py.py", line 89, in run self.build_packages() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build_py.py", line 372, in build_packages self.build_module(module, module_file, package) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/setuptools/command/build_py.py", line 106, in build_module outfile, copied = _build_py.build_module(self, module, module_file, package) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build_py.py", line 333, in build_module "'package' must be a string (dot-separated), list, or tuple") TypeError: 'package' must be a string (dot-separated), list, or tuple % DISTUTILS_DEBUG=t python setup.py nosetests options (after parsing config files): options (after parsing command line): option dict for 'aliases' command: {} option dict for 'nosetests' command: {'all_modules': ('setup.cfg', '1'), 'cover_package': ('setup.cfg', 'foo'), 'detailed_errors': ('setup.cfg', '1'), 'verbosity': ('setup.cfg', '2'), 'with_coverage': ('setup.cfg', '1'), 'with_doctest': ('setup.cfg', '1')} running nosetests Distribution.get_command_obj(): creating 'nosetests' command object setting options for 'nosetests' command: with_coverage = 1 (from setup.cfg) verbosity = 2 (from setup.cfg) cover_package = foo (from setup.cfg) all_modules = 1 (from setup.cfg) with_doctest = 1 (from setup.cfg) detailed_errors = 1 (from setup.cfg) running egg_info Distribution.get_command_obj(): creating 'egg_info' command object Traceback (most recent call last): File "setup.py", line 58, in <module> setuptools.setup(**_SETUP_ARGS) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/commands.py", line 132, in run self.run_command('egg_info') File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 971, in run_command cmd_obj.ensure_finalized() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 109, in ensure_finalized self.finalize_options() File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/setuptools/command/egg_info.py", line 103, in finalize_options self.ensure_dirname('egg_base') File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 269, in ensure_dirname "'%s' does not exist or is not a directory") File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 255, in _ensure_tested_string val = self._ensure_stringlike(option, what, default) File ".../Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 216, in _ensure_stringlike "'%s' must be a %s (got `%s`)" % (option, what, val) distutils.errors.DistutilsOptionError: 'egg_base' must be a directory name (got `src`) % ... # Comment out unicode_literals line in setup.py % python setup.py nosetests running nosetests running egg_info writing src/foo.egg-info/PKG-INFO writing namespace_packages to src/foo.egg-info/namespace_packages.txt writing top-level names to src/foo.egg-info/top_level.txt writing dependency_links to src/foo.egg-info/dependency_links.txt reading manifest file 'src/foo.egg-info/SOURCES.txt' writing manifest file 'src/foo.egg-info/SOURCES.txt' running build_ext Doctest: foo.base.pity.Foo ... ok testFoo (test.base.pity.TestFoo) ... ok Name Stmts Miss Cover Missing --------------------------------------------- foo 3 0 100% foo.base 0 0 100% foo.base.pity 9 0 100% --------------------------------------------- TOTAL 12 0 100% ---------------------------------------------------------------------- Ran 2 tests in 0.034s OK ---------- files: foo_test.zip messages: 724 nosy: mbogosian priority: bug status: unread title: setuptools breaks with from __future__ import unicode_literals in setup.py Added file: http://bugs.python.org/setuptools/file92/foo_test.zip _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue152> _______________________________________________

3 2

Buildout 2.2.0 released
by Jim Fulton July 5, 2013

July 5, 2013

zc.buildout 2.2.0 has been released to PyPI. The main feature of this release is support for setuptools 0.7 and later. See: https://pypi.python.org/pypi/zc.buildout/2.2.0#id3 for a full list of changes. To get this release, you need to download and run a new bootstrap.py file from: http://downloads.buildout.org/2/bootstrap.py Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton

2 1

g.pypi.python.org out of date
by Donald Stufft July 4, 2013

July 4, 2013

It appears the "g" mirror is ~10 days out of date. Do we know who owns it? It needs kicked to start back up or we need to remove it from the pool if we can't get it going again. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

1 0