Mailman 3 August 2011 - Distutils-SIG

Having trouble with pip install
by Vladik Rikhter 24 Aug '11

24 Aug '11

Hi (excuse the n00b like question, but I'm lost at this point): I've been trying to install my requirements.txt file with pip through Cygwin. I went through and ran the easy_install, worked without a problem. I then tried to execute the following command: "pip install -r requirements.txt" Unfortunately the following error came up: > Downloading/unpacking git+http://github.com/tropo/tropo-webapi-python.git(from > -r requirements.txt (line 9)) > Cloning http://github.com/tropo/tropo-webapi-python.git to > /tmp/pip-E3epk3-bui > ld > Running setup.py egg_info for package from git+ > http://github.com/tropo/tropo-w > ebapi-python.git > 1 [main] python2.6 9848 C:\cygwin\bin\python2.6.exe: *** fatal error > - una > ble to remap \\?\C:\cygwin\lib\python2.6\lib-dynload\time.dll to same > address as > parent: 0x360000 != 0x3F0000 > Stack trace: > Frame Function Args > 00289F08 6102796B (00289F08, 00000000, 00000000, 00000000) > 0028A1F8 6102796B (6117EC60, 00008000, 00000000, 61180977) > 0028B228 61004F1B (611A7FAC, 61243884, 00360000, 003F0000) > End of stack trace > 1 [main] python2.6 11796 fork: child 9848 - died waiting for dll > loading, > errno 11 > Error [Errno 11] Resource temporarily unavailable while executing > command py > thon setup.py egg_info > Exception: > Traceback (most recent call last): > File > "/usr/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/basecommand.py" > , line 126, in main > self.run(options, args) > File > "/usr/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/commands/instal > l.py", line 223, in run > requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, > bundl > e=self.bundle) > File "/usr/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/req.py", > line 9 > 86, in prepare_files > req_to_install.run_egg_info() > File "/usr/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/req.py", > line 2 > 22, in run_egg_info > command_desc='python setup.py egg_info') > File > "/usr/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/__init__.py", l > ine 220, in call_subprocess > cwd=cwd, env=env) > File "/usr/lib/python2.6/subprocess.py", line 633, in __init__ > errread, errwrite) > File "/usr/lib/python2.6/subprocess.py", line 1049, in _execute_child > self.pid = os.fork() > OSError: [Errno 11] Resource temporarily unavailable > Storing complete log in /home/Vladik/.pip/pip.log Would love some help on how to fix this! Thank you, thank you! -- (c) 404.966.9048

1 0

Dependency problems.
by Mac Ryan 23 Aug '11

23 Aug '11

Hello, I just subscribed yesterday, having being redirected here from the python-tutor ML. I hope this is the right place to ask the question I am struggling with. I am trying to package a program I wrote for debian. It's my **very first time** with packaging at all, and also with distutils, so I followed online documentation to get something done. It work-ish'ed, but I am struggling with a problem on dependencies. To write my setup.py script I followed this: http://packages.python.org/distribute/setuptools.html#automatic-script-crea… In the section on dependencies it says: "If your project depends on packages that aren’t registered in PyPI, you may still be able to depend on them, as long as they are available for download as an egg, in the standard distutils sdist format, or as a single .py file. You just need to add some URLs to the dependency_links argument to setup()." My question is: how do I list dpendencies that are not python code? For example: say my program needs to launch at some point another program like for example inkscape, is there a way to specify this in the setup.py file, or am I out of luck and my only chance is to list it in the debian directory half-way through the process of converting my code to a .deb package? Also, another question out of scientific curiosity. On a debian-based distro, if a python module is installed via PyPI, will it be "seen" and handled by apt-get / synaptic as if it were installed from a .deb package? In other words: would a user be able to execute `apt-get remove xxxx` if xxxx has been installed with python easy_install xxxx`? Thank you in advance for your help! /mac

4 5

stdeb bug?
by Mac Ryan 22 Aug '11

22 Aug '11

After having wasted some more hours in trying to understand why I can't package data_files in the same directory of the python modules (see my previous post to the ML) I begin to believe I might have hit a bug in stdeb... In fact the setup.py script that I wrote works fine with python setup.py sdist (the tar.gz that is being generated has both my module and data file in the same directory) but it throws errors when I run: python setup.py --command-packages=stdeb.command bdist_deb specifically it says: warning: install_data: setup script did not provide a directory for '' -- installing right in '/home/<mydirectory>/debian/python-<myapplicationname>/usr' error: can't copy '': doesn't exist or not a regular file in my setup.py: py_modules = ['src/prog'], data_files=['', ['src/data.yml']], so I believe stdeb is simply unable to understand that the empty string means "put the data file together with the module", the way the regular distutils can. Am I right? Any workaround to suggest? Thank you in advance, /mac

1 0

[Python Language Summit] Distutils / Packaging surveyfrom Sabrina
by Sabrina Friedman 18 Aug '11

18 Aug '11

On Sat, 31 Jan 2009 10:37:56 -0500, "P.J. Eby" <pje at telecommunity.com> wrote: > If this is true, then there's no need to distinguish between .py > files and any other data files - they both belong in /share to begin > with, not in /lib. Or else they ALL belong in /lib. The entire "FHS > demands they be split" concept is wrong from the get-go, under that > interpretation. Not taking away from that.... but in windows things have their own directories too and python files should go in the right places also. Best place for packages -> \Program Files\Common Files\Python x.x\Packages Best place for python -> \Program Files\Python x.x Under linux - Best place for packages -> /usr/local/Python x.x/Packages. (a python developer shouldn't go looking in system directories for a source package he may want to look at) Putting files where people expect to find them, doesn't cost more. The only reason things are the way they are is because of history. But at the same time, if we want our software to "live" in an operating system we must follow their rules to be regarded as good citizens. :-) Regards David Sabrina Friedman Billige Flüge Marketing GmbH Emanuelstr. 3, 10317 Berlin Deutschland Telefon: +49 (33) 5310967 Email: utebachmeier(a)gmail.com Site: http://flug.airego.de - Billige Flüge vergleichen

1 0

[PATCH] Letting distribute try different download URLs
by Asheesh Laroia 18 Aug '11

18 Aug '11

Hi all, I have a very real-world problem I'm hitting with distribute, and I'm proposing a patch. Right now, PyPI points to a tar.gz for the 'nose' package that returns Searching for nose==1.0.0 Reading http://pypi.python.org/simple/nose/ Reading http://somethingaboutorange.com/mrl/projects/nose/ Reading http://readthedocs.org/docs/nose/ Best match: nose 1.0.0 Downloading http://somethingaboutorange.com/mrl/projects/nose/nose-1.0.0.tar.gz error: Can't download http://somethingaboutorange.com/mrl/projects/nose/nose-1.0.0.tar.gz: 404 Not Found I propose that if distribute hits a HTTP error like this, it keeps looping and tries the next available tar.gz for nose. In my case, I think it then succeed because I have dependency_links in my setup() call (in my setup.py) that point to where I have been stashing copies of my own dependencies: http://linode.openhatch.org/~paulproteus/ So I propose this patch. It is pretty straightforward. I hope that you accept it, and if not, that you explain why. I have re-run the test suite after the addition of my patch, and it does not break any existing tests. -- Asheesh.

1 0

Re: [Distutils] "buildout-versions" not showing pinned versions
by Chris Withers 17 Aug '11

17 Aug '11

Hi, I've CC'ed in the correct mailing list for these discussions, you should mail there first in future. Right, replaying our discussion in it's original order: > On 13/08/2011 04:04, B.Nanda Kishore wrote: > > when my buildout.cfg is having content like: > *[buildout]* > *parts = deps* > *extensions = buildout-versions* > * > * > *[deps]* > *recipe = zc.recipe.egg* > *eggs = Django* > > and when I run buildout its printing the latest Django version(1.3). > Thats fine. But..... > when I pin the version number of Django in buildout.cfg to something Okay, so it looks like you're pinning versions as follows: On 15/08/2011 06:20, B.Nanda Kishore wrote: > Here is my buildout.cfg: > [buildout] > parts = deps > extensions = buildout-versions > > [deps] > recipe = zc.recipe.egg > eggs = *Django==1.0.4* As an aside, I'll point out that the above buildout.cfg doesn't do anything useful as Django doesn't expose any setuptools-style console scripts. Now, buildout-versions won't report any versions here since you've pinned Django to 1.0.4. It only warns about un-pinned versions of eggs. Here's a minimal useful recipe that pins Django in a more orthodox fashion and provides a bin/py interpreter that will that version 1.0.4 of django available: [buildout] parts = deps extensions = buildout-versions versions = versions [versions] buildout-versions = 1.6 Django = 1.0.4 setuptools = 0.6c12dev-r88846 zc.buildout = 1.5.2 zc.recipe.egg = 1.3.2 [deps] recipe = zc.recipe.egg eggs = Django interpreter = py However, I'd suggest looking at the djangorecipe package as a much more useful way of dealing with Django in buildout! cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

4 7

Which buildout to use?
by Reinout van Rees 17 Aug '11

17 Aug '11

Hi, There's buildout 1.4.4, 1.5.2 and an alpha of 2.0. The 2.0 seems to aim at python 3 and is, according to the docs, in a very early alpha stage, so I'll leave that one out. What I'm using now is 1.4.4 with the special bootstrap.py that ensures it picks 1.4.4 instead of a newer one. The reason: it works with http://pypi.python.org/pypi/osc.recipe.sysegg which finds system wide python packages (numpy and other stuff better installed through the OS). I tried 1.5.x half a year ago, but it didn't find numpy&friends on ubuntu even though 1.5 is supposed to allow just that. I tried it this morning on OSX with 1.5.2 but still no luck. It doesn't want to find the OS-level packages. But... sticking to ye olde 1.4.4 seems wrong to me. So I phoned my brother Maurits (hi!) who is working with plone: plone is a heavy buildout user, so what's the status there? He said plone is basically also still on 1.4.4! a) I feel a bit better sticking to 1.4.4, knowing that plone also does it. b) Is anyone actually using 1.5.2 with system packages? And by that I mean that you have a dependency on something like numpy and buildout actually finds that package locally and won't try and grab it off pypi? Am I doing something wrong? I dare say I've got an above average experience with buidout and I just can't get this to work. Reinout p.s.: Here's my buildout config. Am I doing something completely wrong? [buildout] parts = scripts include-site-packages = true allowed-eggs-from-site-packages = numpy [scripts] recipe = zc.recipe.egg eggs = numpy -- Reinout van Rees http://reinout.vanrees.org/ reinout(a)vanrees.org http://www.nelen-schuurmans.nl/ "If you're not sure what to do, make something. -- Paul Graham"

7 13

buildout-versions now on github
by Chris Withers 16 Aug '11

16 Aug '11

Hi All, In an effort to make it easier to get involved, I've moved buildout-versions to github: https://github.com/Simplistix/buildout-versions cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 2

"Safe" Project Names and underscores in Project Names issue
by Michael 04 Aug '11

04 Aug '11

Forgive me if I ask a stupid question but what characters are allowed in a project name on PyPI and by Distribute/Setuptools? I specifically ask because of what I think is a problem I found with Distribute/Setuptools with the underscore character ("_") It seems PyPI allows underscore as a valid character in a project name and as such there are projects like pyramid_beaker, django_email_auth. Distributes' behaviour is to replace all underscores to dashes using the safe_name function (https://bitbucket.org/tarek/distribute/src/611910892a04/pkg_resources.py#cl…). Project name is registered with dashes in the egg (i.e pyramid-beaker) and nowhere is the original name stored. It seems, following lead Pip has adjusted its code accordingly (https://github.com/pypa/pip/blob/ea60bb79b5f837f0aa36d2354415dbcca5368afe/p…) As such, modifying the safe_name method to recognize undescore breaks pip. Doing "pip install pyramid_beaker" installs the package successfully however any package tools (i.e pip) report the project as "pyramid-beaker" and as such becomes unusable name if PyPI is queried via RPC Interfaces. Trying to turn all the dashes back underscores breaks packages that have underscores in them (i.e. sphinxcontrib-programoutput). And if the package were to use both, it would be impossible to determine what it is without running all the permutations. I would appreciate if any one could advise me on this matter and let me know if this is a bug underscore treatment with Distribute/Setuptools, pip or PyPI. Here is the test code to reproduce the problem (in a virtualenv): 1. Setup a test virtualenv with "--distribute --no-site-packages" and activate it 2. Install following packages: pip install --ignore-installed --no-deps pyramid_beaker pip install --ignore-installed --no-deps sphinxcontrib-programoutput 3. Save and run the following script that uses pip and XMLRPC to check for new versions: -------------------------------- import xmlrpclib import pip pypi = xmlrpclib.ServerProxy('http://pypi.python.org/pypi') for dist in pip.get_installed_distributions(): available = pypi.package_releases(dist.project_name) if not available: # Try to capitalize pkg name available = pypi.package_releases(dist.project_name.capitalize()) if not available: msg = 'no releases at pypi' elif available[0] != dist.version: msg = '{} available'.format(available[0]) else: msg = 'up to date' pkg_info = '{dist.project_name} {dist.version}'.format(dist=dist) print '{pkg_info:40} {msg}'.format(pkg_info=pkg_info, msg=msg) --------------------------------- Output (specific to installed packages): sphinxcontrib-programoutput 0.4.1 up to date pyramid-beaker 0.5 no releases at pypi [pyramid-beaker does not exist on PyPI, since its pyramid_beaker) Expected output (mind the underscores) sphinxcontrib-programoutput 0.4.1 up to date pyramid_beaker 0.5 up to date ---- Additional info --- pyramid_beaker-0.5-py2.7.egg-info/PKG-INFO shows that the project name is: Name: pyramid-beaker

2 1

[issue131] Shebang for gui_scripts on Windows is not changed to pythonw
by Florian 04 Aug '11

04 Aug '11

New submission from Florian <florian.dorn(a)gmail.com>: When creating a wininst, get_script_header alwasy sets the executabe to "python.exe". Thus, in get_script_args() the code to check if the header should actually be changed should be updated to: if os.path.exists(new_header[2:-1]) or wininst or sys.platform!='win32': hdr = new_header else: hdr = header ---------- messages: 630 nosy: flocki priority: bug status: unread title: Shebang for gui_scripts on Windows is not changed to pythonw _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue131> _______________________________________________

1 0