Mailman 3 March 2006 - Distutils-SIG

easy_install problem with Twisted-2.1.0
by titus＠caltech.edu 05 Mar '06

05 Mar '06

Hi all, here's a quick bug report for ya. Happened with both Python 2.3 and 2.4, using latest easy_install. % easy_install Twisted-2.1.0.tar.bz2 Processing Twisted-2.1.0.tar.bz2 Running Twisted-2.1.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-5-YDh-/Twisted-2.1.0/egg-dist-tmp-9yveKV Traceback (most recent call last): File "/usr/bin/easy_install2.4", line 7, in ? sys.exit( File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 1138, in main setup(script_args = ['-q','easy_install', '-v']+argv, **kw) File "/usr/lib/python2.4/distutils/core.py", line 149, in setup dist.run_commands() File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands self.run_command(cmd) File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command cmd_obj.run() File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 230, in run self.easy_install(spec, not self.no_deps) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 303, in easy_install return self.install_item(None, spec, tmpdir, deps, True) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 338, in install_item dists = self.install_eggs(spec, download, tmpdir) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 532, in install_eggs return self.build_and_install(setup_script, setup_base) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 807, in build_and_install self.run_setup(setup_script, setup_base, args) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/easy_install.py", line 796, in run_setup run_setup(setup_script, args) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/sandbox.py", line 26, in run_setup DirectorySandbox(setup_dir).run( File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/sandbox.py", line 63, in run return func() File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/sandbox.py", line 29, in <lambda> {'__file__':setup_script, '__name__':'__main__'} File "setup.py", line 113, in ? File "./twisted/python/dist.py", line 69, in setup File "/usr/lib/python2.4/distutils/core.py", line 149, in setup dist.run_commands() File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands self.run_command(cmd) File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command cmd_obj.run() File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/bdist_egg.py", line 167, in run self.run_command("egg_info") File "/usr/lib/python2.4/distutils/cmd.py", line 333, in run_command self.distribution.run_command(command) File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command cmd_obj.run() File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/egg_info.py", line 129, in run writer(self, ep.name, os.path.join(self.egg_info,ep.name)) File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/egg_info.py", line 321, in write_toplevel_names pkgs = dict.fromkeys( File "/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/dist.py", line 630, in iter_distribution_names yield ext.name AttributeError: 'bool' object has no attribute 'name'

3 2

Re: [Distutils] Paste broken? (likely setuptools installation problem)
by Ben Bangert 04 Mar '06

04 Mar '06

On Mar 3, 2006, at 1:27 PM, Robert Leftwich wrote: > In an attempt to solve this problem and get Pylons working again > I've spent the > last 2hrs trying various approaches - ending up with deleting > everything even > remotely connected to my app and Pylons from the site-packages, > cleaning up > easy-install.pth to remove all references, deleting all eggs - > basically > everything I could find, even to the point of blowing away ez- > setup.py. I'm trying to reproduce this problem, clearing Paste and running easy_install appears to fetch it all properly. I've done this on several different machines (FreeBSD 4.2, FreeBSD 5.2, OSX 10.4), I can't seem to reproduce it anywhere. I'm cc'ing dist-utils on this as it appears to be an issue with setuptools. > Running python ez_setup.py Pylons==dev results in: > > ... (some successful installs elided) > > Installed /usr/lib/python2.4/site-packages/PasteScript-0.5dev_r4816- > py2.4.egg > Searching for PasteDeploy==dev,>=0.5dev-r4624 > Reading http://www.python.org/pypi/PasteDeploy/ > Reading http://pythonpaste.org/deploy/ > Best match: PasteDeploy dev > Downloading http://svn.pythonpaste.org/Paste/Deploy/ > trunk#egg=PasteDeploy-dev > Doing subversion checkout from http://svn.pythonpaste.org/Paste/ > Deploy/trunk to > /tmp/easy_install-9WT2is/trunk > Processing trunk > Running setup.py -q bdist_egg --dist-dir > /tmp/easy_install-9WT2is/trunk/egg-dist-tmp-s4UzvR > warning: manifest_maker: standard file not found: should have one > of README, > README.txt > warning: no files found matching 'docs/*.html' > warning: no previously-included files found matching 'docs/rebuild' > ---------------------------------------------------------------------- > --- > CONFLICT WARNING: > > The following modules or packages have the same names as modules or > packages being installed, and will be *before* the installed > packages in > Python's search path. You MUST remove all of the relevant files and > directories before you will be able to use the package(s) you are > installing: > > /usr/lib/python2.4/site-packages/PasteScript-0.5dev_r4816- > py2.4.egg/paste > > Note: you can attempt this installation again with EasyInstall, and > use > either the --delete-conflicting (-D) option or the > --ignore-conflicts-at-my-risk option, to either delete the above files > and directories, or to ignore the conflicts, respectively. Note > that if > you ignore the conflicts, the installed package(s) may not work. > Running with -D succeeds (sort of), except that doing a "paster create > --template=pylons test" fails with: > > > Traceback (most recent call last): > File "/usr/bin/paster", line 5, in ? > pkg_resources.run_script('PasteScript==0.5dev-r4816', 'paster') > File > "/usr/lib/python2.4/site-packages/setuptools-0.6a11dev_r42684- > py2.4.egg/pkg_resources.py", > line 407, in run_script > self.require(requires)[0].run_script(script_name, ns) > File > "/usr/lib/python2.4/site-packages/setuptools-0.6a11dev_r42684- > py2.4.egg/pkg_resources.py", > line 1043, in run_script > execfile(script_filename, namespace, namespace) > File > "/usr/lib/python2.4/site-packages/PasteScript-0.5dev_r4816- > py2.4.egg/EGG-INFO/scripts/paster", > line 17, in ? > from paste.script import command > ImportError: No module named script > > I've tried all the combinations I can think of (using setuptools > a10 and dev as > shown above), easy_install and ez_setup.py, even installing the > Paste* dev > releases directly using easy_install, but all w/o success. > > Can anyone offer any alternative approaches to getting Pylons to > work again? Ok, I'm not sure how this is happening but my guess is that for some bizarre reason PasteScript was seen as a conflict to PasteDeploy. When you ran with -D, it of course happily blew away PasteScript during the PasteDeploy installation. So of course, when paster tries to use something from PasteScript, there is no longer any PasteScript registered as being around anymore thus it can't be imported. Perhaps try installing just PasteScript: easy_install -U PasteScript==dev Then run paster again? Alternatively, if something is borked in your setuptools settings somewhere, which cause PasteDeploy to think PasteScript was in conflict... hopefully one of the distutils guys can think of either a reason that would happen, or how you could prevent it from occuring. Hope that helps, Ben

2 1

excluding files from sdist using setuptools?
by Andrew Straw 03 Mar '06

03 Mar '06

How do I do the equivalent of an "exclude" in MANIFEST.in using setuptools? I can't find this documented anywhere.

2 1

Testing with stubbed entry points?
by Iwan Vosloo 02 Mar '06

02 Mar '06

Hi there, I'm trying to write tests for an egg which expects certain entry points to be supplied for an entry point group it is interested in. What is the easiest way (in testing code) to make a new entry point in some group in a test setup, and nuke it again in the test tearDown? Tx -i

2 3

setuptools and ordering...
by Iwan Vosloo 02 Mar '06

02 Mar '06

Hi, I have a package which discovers plugins via pkg_resources.iter_entry_points. Is the order entry points are iterated through defined in any way? Such as first eggs to be loaded first, or some such? There seems to be some kind of ordering, but I don't know if this is intended... My scenario: I have eggs that depend on other eggs. So what I really would like to have is an ordering in the entry points iterator that would guarantee that entry points in distributions that depend on other distributions would be after the entry points from the distributions they depend on. (Since you already specify in setup.py what the dependencies are between Distributions, it makes sense not to duplicate this information in custom code. Such ordering of entry points would make it unnecessary to keep more dependency information.) Failing this, I can either depend on whatever order there is (but from the code it looks like that's a coincidence). Or, I'd have to write code that builds the dependency tree (of Distributions) and then flatten it into a list that would make sense. And THEN search for entry points in that order. I don't suppose something like this exists? -i

2 1

Re: [Distutils] [PEAK] Re: problem with EasyInstall 0.6a10 + pkg manager
by Phillip J. Eby 01 Mar '06

01 Mar '06

At 10:53 AM 3/1/2006, Ronny Pfannschmidt wrote: >Phillip J. Eby wrote: > >>At 09:35 AM 3/1/2006, Ronny Pfannschmidt wrote: >> >>>With the latest version of EasyInstall i had a major problem with the >>>"exhaustive testing of the install directory, including a spawn test for >>>.pth file support" >>>since my pkg manager uses `setup.py install --root=Dest` to install the >>>pkg in a image directory, before installing it on the system. >>> >>>actually i work around this by creating the needed dirs and adding them >>>to PYTHONPATH >>> >>>is there a nicer way too work with such pkg managers ? >> >> >>Yes. Use "setup.py install --single-version-externally-managed >>--root=Dest", which will do the installation in a way that's >>package manager friendly. >> >>I may change this at some point so that a --root (other than /) >>automatically triggers the other option, but at the moment I'm not >>sure whether that would interfere with anything else. >i tried the option, and found several problems >while the python modules where installed fine much of the other data >is thrown right into /usr (wich isnt very nice) > >as result the program (pida) was not working anymore ( while it >worked with the dirty workaround), since it was written for a egg >image, wich implies, that much of the data is in the root of the egg >image and usually the path can be resolved by the module path Ah. Don't do that. If your packages have data, put them inside a package directory, and use the pkg_resources module APIs to access them. Then your code will work no matter how it's installed. I would go so far in fact as to say that you should *never* use the disutils' data files installation for constant data files that your program needs access to at runtime. The "data files" option should be used only for example configuration files, documentation, etc. If your packages need data, install it as package data.

1 0

Re: [Distutils] problem with EasyInstall 0.6a10 + pkg manager
by Phillip J. Eby 01 Mar '06

01 Mar '06

At 09:35 AM 3/1/2006, Ronny Pfannschmidt wrote: >With the latest version of EasyInstall i had a major problem with the >"exhaustive testing of the install directory, including a spawn test for >.pth file support" >since my pkg manager uses `setup.py install --root=Dest` to install the >pkg in a image directory, before installing it on the system. > >actually i work around this by creating the needed dirs and adding them >to PYTHONPATH > >is there a nicer way too work with such pkg managers ? Yes. Use "setup.py install --single-version-externally-managed --root=Dest", which will do the installation in a way that's package manager friendly. I may change this at some point so that a --root (other than /) automatically triggers the other option, but at the moment I'm not sure whether that would interfere with anything else.

1 0