Mailman 3 July 2010 - Distutils-SIG

Distribution downloads by pip (and multiple distribution types)
by Michael Foord 14 Jul '10

14 Jul '10

Hello all, For unittest2 I now have three different distributions. A "version" that supports Python 2.4 - 2.7, one for Python 2.3 that is developed in a separate branch because it makes the code ugly, and a separate distribution for Python 3. The reason I'm not using 2to3 with a single codebase is that unittest2 for Python 3 is *basically* just a straight copy of the unittest package from Python 3.2 (with a few fixes to work in 3.0 and a few other changes that are in unittest2 anyway). Having a single distribution with multiple versions in and having setup.py decide at install time would be another approach, but that plays badly with test discovery. So the challenge is, how do I put all of these up on PyPI and have pip install the right one? pip doesn't make it clear what versions of Python it supports, and the PyPI page doesn't use the trove classifiers (naughty!), but I'm fine with users of the Python 2.3 distribution having to download and install manually. Unfortunately it *seems* that "pip install unittest2" (on Python 2.4 - 2.7) will just install from whichever file was *most recently uploaded* to the PyPI page - even if it is marked as not a source distribution and has Python 2.3 in the name. So, the good news is that if you've used pip to install unittest2 in the last few days you've got the Python 2.3 version. It is feature complete with tests, so that shouldn't actually be a problem. As far as I can tell the only way I can solve this is to remove the Python 2.3 download from PyPI and host it separately, which is what I've now done. (Download link on the PyPI page if you need it.) Similarly I guess there is no way to have a Python 3 distribution under the same project and have pip install the correct distribution under the correct version of Python. To get round this I have created a separate project: unittest2py3k. It still installs the same *package name*, just has a different project name. Now if distutils2 could solve these problems, that would be great. :-) I'm aware that setuptools / distribute allows you to provide (what are effectively binary) distributions for specific Python versions, but I need to support pip too. It would also be great if there was a way of specifying "this distribution is for Python 2.4 - 2.7", or even "any version of Python 2 after 2.4". All the best, Michael -- http://www.voidspace.org.uk

1 0

[buildout] buildout 1.5 sometime ever please?
by Martijn Faassen 14 Jul '10

14 Jul '10

Hi there, I've been waiting for years for a release of buildout that contains proper isolation from Python's site-packages. The non-isolation is a major flaw in buildout that makes it SO much harder to write proper installation instructions for software such as Grok. We need to wrap Grok's buildout installation using virtualenv --no-site-packages. I just discovered that this installation actually fails if I use an ubuntu-installed virtualenv (or setuptools)! It works with a manually installed version of either, and I'm sure the problem is somewhere in z3c.autoinclude too, but it's still an issue. Last year in september I hacked up some code that would do the isolation. I was then informed that Gary Poster was working on a branch instead, and indeed the branch I saw then looked much improved in features. So I waited. I saw new versions of the branch come and go and I'm not sure what's going on, but I waited. I noticed that in april there was a beta release of buildout that featured such improvements. This release was then withdrawn and overridden with 1.50b2 with the message: "This is a re-release of 1.4.3 to hide the brown-bag release of 1.5.0b1. The changes in 1.5.0b1 will reappear as 1.5.0 soon, when the additional reported problems have been addressed." It is now july, so I'm starting to get my doubts about the word "soon". Have the reported problems been addressed? Is there any hope I can get a buildout that actually provides proper isolation sometime? Can I help? Regards, Martijn

8 33

Installing distribute with Python 3.0 / 3.1
by Michael Foord 14 Jul '10

14 Jul '10

I get the following error attempting to install distribute 0.6.13 with Python 3.0 / 3.1: python3.0 setup.py install creating build creating build/src creating build/src/docs creating build/src/docs/_templates creating build/src/docs/_theme creating build/src/docs/_theme/nature creating build/src/docs/_theme/nature/static creating build/src/setuptools creating build/src/setuptools/command creating build/src/setuptools/tests creating build/src/tests creating build/src/tests/shlib_test copying setuptools/__init__.py -> build/src/setuptools copying setuptools/archive_util.py -> build/src/setuptools copying setuptools/depends.py -> build/src/setuptools copying setuptools/dist.py -> build/src/setuptools copying setuptools/extension.py -> build/src/setuptools copying setuptools/package_index.py -> build/src/setuptools copying setuptools/sandbox.py -> build/src/setuptools copying setuptools/tests/__init__.py -> build/src/setuptools/tests copying setuptools/tests/doctest.py -> build/src/setuptools/tests copying setuptools/tests/server.py -> build/src/setuptools/tests copying setuptools/tests/test_build_ext.py -> build/src/setuptools/tests copying setuptools/tests/test_develop.py -> build/src/setuptools/tests copying setuptools/tests/test_easy_install.py -> build/src/setuptools/tests copying setuptools/tests/test_packageindex.py -> build/src/setuptools/tests copying setuptools/tests/test_resources.py -> build/src/setuptools/tests copying setuptools/tests/test_sandbox.py -> build/src/setuptools/tests copying setuptools/tests/test_upload_docs.py -> build/src/setuptools/tests copying setuptools/command/__init__.py -> build/src/setuptools/command copying setuptools/command/alias.py -> build/src/setuptools/command copying setuptools/command/bdist_egg.py -> build/src/setuptools/command copying setuptools/command/bdist_rpm.py -> build/src/setuptools/command copying setuptools/command/bdist_wininst.py -> build/src/setuptools/command copying setuptools/command/build_ext.py -> build/src/setuptools/command copying setuptools/command/build_py.py -> build/src/setuptools/command copying setuptools/command/develop.py -> build/src/setuptools/command copying setuptools/command/easy_install.py -> build/src/setuptools/command copying setuptools/command/easy_install2.py -> build/src/setuptools/command copying setuptools/command/egg_info.py -> build/src/setuptools/command copying setuptools/command/install.py -> build/src/setuptools/command copying setuptools/command/install_egg_info.py -> build/src/setuptools/command copying setuptools/command/install_lib.py -> build/src/setuptools/command copying setuptools/command/install_scripts.py -> build/src/setuptools/command copying setuptools/command/register.py -> build/src/setuptools/command copying setuptools/command/rotate.py -> build/src/setuptools/command copying setuptools/command/saveopts.py -> build/src/setuptools/command copying setuptools/command/sdist.py -> build/src/setuptools/command copying setuptools/command/setopt.py -> build/src/setuptools/command copying setuptools/command/test.py -> build/src/setuptools/command copying setuptools/command/upload.py -> build/src/setuptools/command copying setuptools/command/upload_docs.py -> build/src/setuptools/command copying setuptools/tests/win_script_wrapper.txt -> build/src/setuptools/tests copying setuptools/cli.exe -> build/src/setuptools copying setuptools/gui.exe -> build/src/setuptools copying tests/install_test.py -> build/src/tests copying tests/manual_test.py -> build/src/tests copying tests/test_distribute_setup.py -> build/src/tests copying tests/shlib_test/setup.py -> build/src/tests/shlib_test copying tests/shlib_test/test_hello.py -> build/src/tests/shlib_test copying tests/shlib_test/hello.c -> build/src/tests/shlib_test copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test copying tests/api_tests.txt -> build/src/tests RefactoringTool: Skipping implicit fixer: buffer RefactoringTool: Skipping implicit fixer: idioms RefactoringTool: Skipping implicit fixer: set_literal RefactoringTool: Skipping implicit fixer: ws_comma --- build/src/tests/api_tests.txt (original) +++ build/src/tests/api_tests.txt (refactored) @@ -39,7 +39,7 @@ >>> dist.py_version == sys.version[:3] True - >>> print dist.platform + >>> print(dist.platform) None Including various computed attributes:: @@ -199,7 +199,7 @@ You can ask a WorkingSet to ``find()`` a distribution matching a requirement:: >>> from pkg_resources import Requirement - >>> print ws.find(Requirement.parse("Foo==1.0")) # no match, return None + >>> print(ws.find(Requirement.parse("Foo==1.0"))) # no match, return None None >>> ws.find(Requirement.parse("Bar==0.9")) # match, return distribution @@ -211,7 +211,7 @@ >>> try: ... ws.find(Requirement.parse("Bar==1.0")) ... except VersionConflict: - ... print 'ok' + ... print('ok') ok You can subscribe a callback function to receive notifications whenever a new @@ -219,7 +219,7 @@ once for each existing distribution in the working set, and then is called again for new distributions added thereafter:: - >>> def added(dist): print "Added", dist + >>> def added(dist): print("Added", dist) >>> ws.subscribe(added) Added Bar 0.9 >>> foo12 = Distribution(project_name="Foo", version="1.2", location="f12") RefactoringTool: Files that were modified: RefactoringTool: build/src/tests/api_tests.txt copying docs/conf.py -> build/src/docs copying docs/easy_install.txt -> build/src/docs copying docs/index.txt -> build/src/docs copying docs/pkg_resources.txt -> build/src/docs copying docs/python3.txt -> build/src/docs copying docs/roadmap.txt -> build/src/docs copying docs/setuptools.txt -> build/src/docs copying docs/using.txt -> build/src/docs copying docs/_theme/nature/theme.conf -> build/src/docs/_theme/nature copying docs/_theme/nature/static/pygments.css -> build/src/docs/_theme/nature/static copying docs/_theme/nature/static/nature.css_t -> build/src/docs/_theme/nature/static copying docs/Makefile -> build/src/docs copying docs/_templates/indexsidebar.html -> build/src/docs/_templates copying distribute_setup.py -> build/src copying easy_install.py -> build/src copying pkg_resources.py -> build/src copying setup.py -> build/src copying site.py -> build/src copying CHANGES.txt -> build/src copying CONTRIBUTORS.txt -> build/src copying DEVGUIDE.txt -> build/src copying pip-log.txt -> build/src copying README.txt -> build/src copying MANIFEST.in -> build/src copying launcher.c -> build/src Skipping implicit fixer: buffer Skipping implicit fixer: idioms Skipping implicit fixer: set_literal Skipping implicit fixer: ws_comma Before install bootstrap. Scanning installed packages No setuptools distribution found running install Traceback (most recent call last): File "setup.py", line 211, in <module> scripts = scripts, File "/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/distutils/core.py", line 149, in setup dist.run_commands() File "/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/distutils/dist.py", line 942, in run_commands self.run_command(cmd) File "/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/distutils/dist.py", line 962, in run_command cmd_obj.run() File "build/src/setuptools/command/install.py", line 73, in run self.do_egg_install() File "build/src/setuptools/command/install.py", line 82, in do_egg_install easy_install = self.distribution.get_command_class('easy_install') File "build/src/setuptools/dist.py", line 361, in get_command_class self.cmdclass[command] = cmdclass = ep.load() File "build/src/pkg_resources.py", line 1954, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "build/src/setuptools/command/easy_install.py", line 16, in <module> from setuptools.sandbox import run_setup File "build/src/setuptools/sandbox.py", line 232, in <module> WRITE_FLAGS = reduce( NameError: name 'reduce' is not defined bigmac:distribute-0.6.13 michael$ python3.1 setup.py install Before install bootstrap. Scanning installed packages No setuptools distribution found running install Traceback (most recent call last): File "setup.py", line 211, in <module> scripts = scripts, File "/Library/Frameworks/Python.framework/Versions/3.1/lib/python3.1/distutils/core.py", line 149, in setup dist.run_commands() File "/Library/Frameworks/Python.framework/Versions/3.1/lib/python3.1/distutils/dist.py", line 919, in run_commands self.run_command(cmd) File "/Library/Frameworks/Python.framework/Versions/3.1/lib/python3.1/distutils/dist.py", line 938, in run_command cmd_obj.run() File "build/src/setuptools/command/install.py", line 73, in run self.do_egg_install() File "build/src/setuptools/command/install.py", line 82, in do_egg_install easy_install = self.distribution.get_command_class('easy_install') File "build/src/setuptools/dist.py", line 361, in get_command_class self.cmdclass[command] = cmdclass = ep.load() File "build/src/pkg_resources.py", line 1954, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "build/src/setuptools/command/easy_install.py", line 16, in <module> from setuptools.sandbox import run_setup File "build/src/setuptools/sandbox.py", line 232, in <module> WRITE_FLAGS = reduce( NameError: name 'reduce' is not defined -- http://www.voidspace.org.uk

1 0

Re: [Distutils] [issue111] Windows: easy_install tries to download X11 PyQT
by P.J. Eby 14 Jul '10

14 Jul '10

FYI, PyQT can't be easy_installed, period, because it's not a distutils-based package. Even if you downloaded the correct version (either manually or by giving the exact URL to easy_install), it still wouldn't work, and there's nothing that can be done about it on the easy_install side. Sorry. At 07:06 PM 7/13/2010 +0000, Erik Hahn wrote: >On Windows, easy_install tries to install the X11 version of PyQT: > >D:\code>c:\Python26\Scripts\easy_install.exe pyqt >install_dir C:\Python26\Lib\site-packages\ >Searching for pyqt >Reading http://pypi.python.org/simple/pyqt/ >Reading http://www.riverbankcomputing.com/software/pyqt/ >Reading http://www.riverbankcomputing.com/software/pyqt/download >Best match: PyQt x11-gpl-4.7.4 >Downloading >http://www.riverbankcomputing.com/static/Downloads/PyQt4/PyQt-x11-gp >l-4.7.4.tar.gz >Processing PyQt-x11-gpl-4.7.4.tar.gz >error: Couldn't find a setup script in >c:\dokume~1\erik\lokale~1\temp\easy_insta >ll-qycl5v\PyQt-x11-gpl-4.7.4.tar.gz

1 0

[issue111] Windows: easy_install tries to download X11 PyQT
by Erik Hahn 13 Jul '10

13 Jul '10

New submission from Erik Hahn <erik_hahn(a)gmx.de>: On Windows, easy_install tries to install the X11 version of PyQT: D:\code>c:\Python26\Scripts\easy_install.exe pyqt install_dir C:\Python26\Lib\site-packages\ Searching for pyqt Reading http://pypi.python.org/simple/pyqt/ Reading http://www.riverbankcomputing.com/software/pyqt/ Reading http://www.riverbankcomputing.com/software/pyqt/download Best match: PyQt x11-gpl-4.7.4 Downloading http://www.riverbankcomputing.com/static/Downloads/PyQt4/PyQt-x11-gp l-4.7.4.tar.gz Processing PyQt-x11-gpl-4.7.4.tar.gz error: Couldn't find a setup script in c:\dokume~1\erik\lokale~1\temp\easy_insta ll-qycl5v\PyQt-x11-gpl-4.7.4.tar.gz ---------- messages: 526 nosy: erik_hahn priority: bug status: unread title: Windows: easy_install tries to download X11 PyQT _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue111> _______________________________________________

1 0

zc.buildout - multiple 'cascading' buildout.cfg files
by Alan Franzoni 13 Jul '10

13 Jul '10

Hello, I'm wondering if there's a way to have something like "local" buildout.cfg files overriding a "master" one; e.g. if buildout.cfg is something like [buildout] parts = one two [one] ... [two] ... I'd like to have something like buildout.cfg.local and insert something like [one] ***** And have the "one" section of buildout.cfg.local override what's set in buildout.cfg, so that buildout acts like [buildout] parts = one two [one] ***** [two] ... had been found. This would be useful because in our projects we usually share one per-project buildout.cfg which every team member uses and it's stored on our VCS, and it's used all around including along our CI server, and we don't want to change it if a real configuration change is unneeded, but often I need to tinker with it (e.g. I want to use one additional development egg, or change a dep, or run a different recipe). Hence I'd like to have the chance to read a buildout.cfg.local - which I could add into the ignore list of our VCS, be it svn, hg or whatever - and leave the master buildout.cfg untouched. Can I do it? If I can't right now, I'll be happy to code and submit a patch. Any thoughts on what's the right approach? e.g. convention-based naming (buildout.cfg.local.001 in the same dir as buildout.cfg, etc). Thank you! -- Alan Franzoni contact me at public(a)[mysurname].eu

2 2

Distribute and Python 3
by Hugo Lopes Tavares 13 Jul '10

13 Jul '10

I am using distribute and python 3.2a0 while I add py3k support to pip this GSoC and I got a problem using distribute: from distutils.sysconfig import _config_vars ImportError: cannot import name _config_vars Well, in Python 3 the distutils.sysconfig pops a DeprecationWarning, because now Python has sysconfig module. As _config_vars is very specific and 2to3 can't convert it, I suggest using some kind of try/except in the source code, like: try: from distutils.sysconfig import _config_vars except ImportError: from sysconfig import _CONFIG_VARS as _config_vars I forked distribute project in bitbucket and added this bugfix, check it here: http://bitbucket.org/hltbra/distribute/changeset/002cccf004e6 I would like to use distribute with this bugfix asap, so, please, upload it to PyPI :)

3 2

buildout dependencies trouble
by John Griessen 12 Jul '10

12 Jul '10

I've been making a buildout.cfg for deploying web sites and hit some snags. django-page-cms is a package I want, and getting it via buildout found eggs for other apps, but needed source for django-page-cms. From there, some requirements, (don't know where they are in the code), pulled in packages django-haystack, django-messages, whoosh, django-mptt-2, and coverage. I think to build the source only absolutely requires django-mptt-2. whoosh and coverage have had problems. buildout found whoosh as a zipped egg and left it zipped even though putting it in the common eggs directory where all others are unzipped and a python path points to them for use when code runs. To get a complete build, I manually unzipped. I'm not moving eggs and downloads to my server, so buildout on the server needed the same treatment. coverage was found OK from my local machine, but not from the server. I'm not sure yet why. I'll try using bin/buidout -D (Debug errors.) soon. Any other suggestions? John

3 2

Can't get "development mode" work as I like it
by Hartmut Goebel 09 Jul '10

09 Jul '10

Hi, I'm used to develop and test from within a single project-directory, without any staging area, etc. As long as I did use scripts, this worked very well. But when switching to pkg_resources entry-points, I get problems: Now I need to ask easy_install (or setup.py develop ...) to create the "scripts" for me. Running python setup.py develop --install-dir . --script-dir . gives an "error: bad install directory or PYTHONPATH" since the current directory is not in PYTHONPATH. I tried other options, too, eg. adding "--editable -b . -N", but with no success. (This very one works as expected, but creates a *.egg-link file which will make the next install recurse until dead.) How can I make easy_install/distribute to generate only the scripts in the current directory? A typical setup for me looks like this: project-a/ setup.py README my_package/ __init__.py ... more stuff ... And I'm working like this: cd project-a # edit my_package/__init__.py ./my-script -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de Monatliche Kolumne: http://www.cissp-gefluester.de/ Goebel Consult mit Mitglied bei http://www.7-it.de

2 1

Re: [Distutils] Python 2.7 is out and ez_setup.py does not work
by P.J. Eby 08 Jul '10

08 Jul '10

At 09:55 AM 7/7/2010 -0300, Hugo Lopes Tavares wrote: >Hi guys, >Python 2.7 was released in July 3, and until now we don't have >ez_setup.py working for that. It looks for an egg for each python >version, and nobody has uploaded that. > >There was a guy here last month with problems to install seutptools in >his Windows, for a similar reason. >Is there so much problem to release bdists for Python 2.7? > >And if you come and say to download the tarball and later install, I >was trying to use virtualenv + Python2.7 and virtualenv uses >ez_setup.py to create virtual environments. > >Could someone upload the bdists and update ez_setup.py? The bdists are done now; there was a bit of a problem with a distutils.command.upload bug introduced here: http://svn.python.org/view/python/trunk/Lib/distutils/command/upload.py?vie… (I'm not sure if this bug is also in 2.6 or not, but for 2.7 I worked around it by having setuptools still use its own upload command. This is a temporary workaround, of course, until 2.7.1 rolls out I suppose.)

1 0