Mailman 3 April 2010 - Distutils-SIG

how to make pip do install using a requirements-files in order?
by mouad ben 30 Apr '10

30 Apr '10

I use pip with distribute and virtualenv to make an automatic install of a Django project . my problem is that i want to make the installation in the order that they came in the requirements-files that i specified. i use this command : pip install -E gold/ -r gold/gold_package.txt and the gold_package.txt : -e svn+https://test/third-party/djangologging#egg=djangologging svn+https://test/spidertools/trunk#egg=spidertools -e svn+https://test/spider/branches/package#egg=spider -e svn+https://test/lib/trunk#egg=lib so it should install djangologging -> spidertools -> spider -> lib , because i have some dependencies that i can't make in the setup.py right now . Best regards Benchchaoui Mouad trainer in www.foobaria.com

2 1

new zc.buildout and virtualenv no longer friends?
by Chris McDonough 30 Apr '10

30 Apr '10

I have a relatively simple buildout that is a directory which is also a virtualenv (the buildout directory was prepped after checkout with Python 2.4 "virtualenv --no-site-packages ." and the bootstrap was run using the resulting "bin/python"). Just now, I had to rerun bin/buildout in that existing directory, and I got this: [chrism@thinko deformsite]$ bin/buildout Getting distribution for 'zc.buildout'. Got zc.buildout 1.5.0b1. Upgraded: zc.buildout version 1.5.0b1; restarting. Generated script '/home/chrism/projects/deformsite/bin/buildout'. Develop: '/home/chrism/projects/deformsite/src/deformsite' Develop: '/home/chrism/projects/deformsite/src/deform' Develop: '/home/chrism/projects/deformsite/src/colander' Getting distribution for 'zc.recipe.egg'. Traceback (most recent call last): File "<string>", line 1, in ? File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/__init__.py", line 2, in ? from setuptools.extension import Extension, Library File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/extension.py", line 1, in ? from distutils.core import Extension as _Extension File "/home/chrism/projects/deformsite/lib/python2.4/distutils/__init__.py", line 3, in ? import warnings ImportError: No module named warnings An error occured when trying to install zc.recipe.egg 1.2.3b1. Look above this message for any errors that were output by easy_install. While: Installing. Getting section deformsite. Initializing section deformsite. Installing recipe zc.recipe.egg. Getting distribution for 'zc.recipe.egg'. Error: Couldn't install: zc.recipe.egg 1.2.3b1 I had built a new virtualenv'ed buildout only a few hours before it the new zc.buildout was released with the most recent releases of everything. I had seen a new release of zc.buildout went up, so I figured I just needed to kinda start from scratch. So subsequently I blew everything away and did what I usually do when I want to start over: chrism@thinko projects]$ svn co $REPOZE_SVN/buildouts/deformsite <snip> Checked out revision 9276. [chrism@thinko projects]$ cd deformsite [chrism@thinko deformsite]$ virtualenv --no-site-packages . New python executable in ./bin/python Installing setuptools.............done. [chrism@thinko deformsite]$ bin/python bootstrap.py Creating directory '/home/chrism/projects/deformsite/parts'. Creating directory '/home/chrism/projects/deformsite/eggs'. Creating directory '/home/chrism/projects/deformsite/develop-eggs'. Getting distribution for 'setuptools'. Got setuptools 0.6c11. But when I went to run it, I got this: Generated script '/home/chrism/projects/deformsite/bin/buildout'. [chrism@thinko deformsite]$ bin/buildout Traceback (most recent call last): File "bin/buildout", line 14, in ? import site # imports custom buildout-generated site.py File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 661, in ? main() File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 628, in main virtual_install_main_packages() File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 546, in virtual_install_main_packages f = open(os.path.join(os.path.dirname(__file__), 'orig-prefix.txt')) IOError: [Errno 2] No such file or directory: '/home/chrism/projects/deformsite/parts/buildout/orig-prefix.txt' If you were paying attention, you'd notice that I made the buildout dir into a virtualenv above, which I've been doing for a long time now to get actual isolation. So at that point, I tried to pin zc.buildout and zc.recipe.egg to an older version by adding the following to my buildout.cfg: versions = versions [versions] zc.buildout = 1.4.3 zc.recipe.egg = 1.2.2 But when I then did the same dance that blew up above with the version pins, it now blew up differently: [chrism@thinko projects]$ cd deformsite [chrism@thinko deformsite]$ virtualenv --no-site-packages . New python executable in ./bin/python Installing setuptools.............done. [chrism@thinko deformsite]$ bin/python bootstrap.py Creating directory '/home/chrism/projects/deformsite/parts'. Creating directory '/home/chrism/projects/deformsite/eggs'. Creating directory '/home/chrism/projects/deformsite/develop-eggs'. Getting distribution for 'setuptools'. Got setuptools 0.6c11. Getting distribution for 'zc.buildout==1.4.3'. Traceback (most recent call last): File "<string>", line 1, in ? File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/__init__.py", line 2, in ? from setuptools.extension import Extension, Library File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/extension.py", line 1, in ? from distutils.core import Extension as _Extension File "/home/chrism/projects/deformsite/lib/python2.4/distutils/__init__.py", line 3, in ? import warnings ImportError: No module named warnings An error occured when trying to install zc.buildout 1.4.3. Look above this message for any errors that were output by easy_install. While: Bootstrapping. Getting distribution for 'zc.buildout==1.4.3'. Error: Couldn't install: zc.buildout 1.4.3 I pdb stepped through this, and it dies when it reexecutes Python via os.spawnle of sys.executable (not on the initial execution of "python bootstrap.py"): [chrism@thinko deformsite]$ bin/python bootstrap.py > /home/chrism/projects/deformsite/bootstrap.py(44)?() -> assert os.spawnle( (Pdb) l 39 40 ws = pkg_resources.working_set 41 42 import pdb; pdb.set_trace() 43 44 -> assert os.spawnle( 45 os.P_WAIT, sys.executable, sys.executable, 46 '-c', cmd, '-mqNxd', tmpeggs, 'zc.buildout', 47 dict(os.environ, 48 PYTHONPATH= 49 (Pdb) p sys.executable, cmd, tmpeggs ('/home/chrism/projects/deformsite/bin/python', 'from setuptools.command.easy_install import main; main()', '/tmp/tmpEduLSX') (Pdb) p ws.find(pkg_resources.Requirement.parse('setuptools')).location '/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg' (Pdb) But sure enough, when I run it with a "real" Python instead of the virtualenv it works. Likely, the recent developers buildout of don't use virtualenv, so they won't have seen this behavior. I don't have the fortitude to debug buildout right now, and the isolation of a virtualenv keeps us sane. Ideally, I could change the buildout.cfg somehow to ignore the new buildout release entirely to get back to a state where buildout could be driven with a virtualenv-Python. Any hints? - C

1 0

Buildout for Python 3
by Sridhar Ratnakumar 30 Apr '10

30 Apr '10

Hi, I have begun porting PyPM along with some dependent modules (cmdln, platinfo) to Python 3. Since I use buildout, I wonder if anyone has already taken up the work of porting it to Python 3. If so, would you need any help in completing it? If no one is currently doing it, I'd be willing to take a stab at working on it myself provided there is some assurance of it getting merged with zc.buildout trunk. Otherwise, I may have to look at alternative setups (virtualenv+pip?). -srid

2 1

[issue107] bdist_egg --bdist-dir param not working quite as expected
by Patrick Ting 30 Apr '10

30 Apr '10

New submission from Patrick Ting <pcting(a)thewhitepixel.com>: So when specifying a build directory through the --bdist-dir param to anything than the default directory: 1. (as expected) a build directory is created, the pyc files are generated in this directory, and then the directory is deleted. 2. (bug) build/ directory in the cwd is always created with the original .py files copied into it. I'm running python v2.6.4 and setuptools v0.6c9 on ubuntu 9.10 amd64 ---------- messages: 515 nosy: pcting priority: bug status: unread title: bdist_egg --bdist-dir param not working quite as expected _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue107> _______________________________________________

1 0

Re: [Distutils] How can I silence setuptools/distutils output in a custom command?
by P.J. Eby 29 Apr '10

29 Apr '10

At 01:58 PM 4/29/2010 -0500, Jason Baker wrote: >On Thu, Apr 29, 2010 at 1:27 PM, P.J. Eby ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com> wrote: >At 01:05 PM 4/29/2010 -0500, Jason Baker wrote: >I've written a simple setuptools command that will read options from >a setup.cfg. The code is here: ><<http://github.com/jasonbaker/rdopts/blob/master/rdopts.py>http://github.com/jasonbaker/rdopts/blob/master/rdopts.py>http://github.com/jasonbaker/rdopts/blob/master/rdopts.py > > >I'd like to be able to use the output of this command to pass to >other programs, but that is a bit difficult when distutils is >writing "running rdopts" out every time I use it. The solution I >found is to just call distutils.log.set_threshold(ERROR) at import >time, but that just feels like a recipe for something to go >wrong. Are there any better ways to do this? > > >python setup.py -q rdopts > > >Ah, I see. I was doing "python setup.py rdopts -q". Is there any >way to make -q enabled by default? Apart from using the alias command (or other config file settings), I don't know of any.

1 0

Re: [Distutils] How can I silence setuptools/distutils output in a custom command?
by P.J. Eby 29 Apr '10

29 Apr '10

At 01:05 PM 4/29/2010 -0500, Jason Baker wrote: >I've written a simple setuptools command that will read options from >a setup.cfg. The code is >here: ><http://github.com/jasonbaker/rdopts/blob/master/rdopts.py>http://github.com/jasonbaker/rdopts/blob/master/rdopts.py > >I'd like to be able to use the output of this command to pass to >other programs, but that is a bit difficult when distutils is >writing "running rdopts" out every time I use it. The solution I >found is to just call distutils.log.set_threshold(ERROR) at import >time, but that just feels like a recipe for something to go >wrong. Are there any better ways to do this? python setup.py -q rdopts

2 1

How can I silence setuptools/distutils output in a custom command?
by Jason Baker 29 Apr '10

29 Apr '10

I've written a simple setuptools command that will read options from a setup.cfg. The code is here: http://github.com/jasonbaker/rdopts/blob/master/rdopts.py I'd like to be able to use the output of this command to pass to other programs, but that is a bit difficult when distutils is writing "running rdopts" out every time I use it. The solution I found is to just call distutils.log.set_threshold(ERROR) at import time, but that just feels like a recipe for something to go wrong. Are there any better ways to do this?

1 0

buildout usage : a setup steps needs access to an installed package
by CP Hennessy 28 Apr '10

28 Apr '10

Hi, I'm relatively new to buildout so this may be a stupid question :) I'm trying to install nltk (Natural Language ToolKit) but it depends on PyYAML. So PyYAML is successfully installed as an egg before nltk. However nltk needs PyYAML during it's installation, but nltk does not have access to the PyYAML egg. How do I configure the buildout to give access to the PyYAML egg to the setup of nltk. Thanks, CPH

3 3

Problem with --uninstall option to setup.py develop
by Warren Weckesser 27 Apr '10

27 Apr '10

I am using version "0.6c9-s1" of setuptools and Python 2.6.4. I am trying to use the --uninstall option of "setup.py develop", but even with a simple example, I get the following error: ----- none:devtest warren$ python setup.py develop --uninstall running develop Traceback (most recent call last): File "setup.py", line 8, in <module> author="WW", File "/Library/Frameworks/Python.framework/Versions/6.1/lib/python2.6/distutils/core.py", line 152, in setup dist.run_commands() File "/Library/Frameworks/Python.framework/Versions/6.1/lib/python2.6/distutils/dist.py", line 975, in run_commands self.run_command(cmd) File "/Library/Frameworks/Python.framework/Versions/6.1/lib/python2.6/distutils/dist.py", line 995, in run_command cmd_obj.run() File "/Library/Frameworks/Python.framework/Versions/6.1/lib/python2.6/site-packages/setuptools/command/develop.py", line 26, in run self._run_egg_info_script(self.distribution.location, AttributeError: Distribution instance has no attribute 'location' none:devtest warren$ ----- My files look like this: devtest/ setup.py qwerty/ __init__.py qwerty.py Running "setup.py develop" works fine. Here's setup.py: ----- from setuptools import setup, find_packages setup( name="qwerty", packages=find_packages(), version="0.1.0", author="WW", ) ----- Is this a known problem, maybe fixed in a later version? Regards, Warren

2 2

PEP 345 and build_requires?
by Sridhar Ratnakumar 27 Apr '10

27 Apr '10

http://goo.gl/zPtX (Google Cache of PEP 345) PEP 345 introduces `Requires-Dist` metadata field that can be used to define *install-time* requirements. Has anyone thought about having a field that can be used to define *build-time* requirement (similar to setuptools' setup_requires?)? Eg: $ grep Build-Requires-Dist lxml-2.2.6/METADATA Build-Requires-Dist: Cython Build-Requires-Dist: Scons $ Or is the only hope to put them all in install_requires/Requires-Dist and have the packagers/installers to resolve and install the dependencies *before* actually attempting to build that module? -srid

1 0