Mailman 3 February 2008 - Distutils-SIG

setuptools - what if a library is required but is in the standard lib?
by Chris Withers 08 Feb '08

08 Feb '08

Hi All, If I mark my package as requiring wsgiref, will it still be downloaded if someone is using python 2.5? If yes, how do I write my setup.py such that it's only required if the installer is using python 2.4 or less? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

4 3

buildout: building shared libraries and using them
by Christian Zagrodnick 07 Feb '08

07 Feb '08

Hi there, we tend to build libxml2, libxslt and lxml in our buildouts together (see below for the config). While building works without any problem, when we use lxml (in tests for instance) the custom built shared libraries are not used but the system libraries. The zc.recipe.egg documentation is quite a bit missleading: rpath: A new-line separated list of directories to search for dynamic libraries at run time. Runtime is apparently referencing the compile time? How could we use the built shared libraries? Should the scripts buildout creates set those paths? Regards, Christian The buildout config: [libxml2] recipe = zc.recipe.cmmi url = http://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/libxml2-2.6.26.tar.gz extra_options = --without-python [libxslt] recipe = zc.recipe.cmmi url = http://ftp.gnome.org/pub/GNOME/sources/libxslt/1.1/libxslt-1.1.16.tar.bz2 extra_options = --with-libxml-prefix=${buildout:directory}/parts/libxml2/ --without-python [lxml] recipe = zc.recipe.egg:custom egg = lxml include-dirs = ${buildout:directory}/parts/libxml2/include/libxml2 ${buildout:directory}/parts/libxslt/include library-dirs = ${buildout:directory}/parts/libxml2/lib ${buildout:directory}/parts/libxslt/lib rpath = ${buildout:directory}/parts/libxml2/lib ${buildout:directory}/parts/libxslt/lib -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

1 1

How to make an egg easy_installable ?
by David Cournapeau 05 Feb '08

05 Feb '08

Hi, I wanted to make an egg from my package, so that people install it with easy_install. I managed to make an egg, which works fine, but I have problems with the cheeseshop, and how easy_install retrieve the egg. First, I uploaded the egg using register and upload command, and I can see the egg on the cheeseshop. But when trying to use easy_install, it does not work: it tries to look for packages in at the URL I gave in url argument, and do not take the egg from the cheeseshop. As a temporary "fix", I removed url and url_download arguments, and re-upload my package: this time, easy_install get the egg, but fails installing it: Creating /usr/media/misc/local/lib/python2.5/site-packages/site.py Searching for numscons Reading http://cheeseshop.python.org/pypi/numscons/ Reading http://cheeseshop.python.org/pypi/numscons/0.3.1 Best match: numscons 0.3.1 Downloading http://pypi.python.org/packages/2.5/n/numscons/numscons-0.3.1-py2.5.egg#md5… Processing numscons-0.3.1-py2.5.egg creating /usr/media/misc/local/lib/python2.5/site-packages/numscons-0.3.1-py2.5.egg Extracting numscons-0.3.1-py2.5.egg to /usr/media/misc/local/lib/python2.5/site-packages Traceback (most recent call last): File "/usr/bin/easy_install", line 8, in <module> load_entry_point('setuptools==0.6c6', 'console_scripts', 'easy_install')() File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1670, in main with_ei_usage(lambda: File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1659, in with_ei_usage return f() File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1674, in <lambda> distclass=DistributionWithoutHelpCommands, **kw File "distutils/core.py", line 151, in setup File "distutils/dist.py", line 974, in run_commands File "distutils/dist.py", line 994, in run_command File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 211, in run self.easy_install(spec, not self.no_deps) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 446, in easy_install return self.install_item(spec, dist.location, tmpdir, deps) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 471, in install_item dists = self.install_eggs(spec, download, tmpdir) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 619, in install_eggs return [self.install_egg(dist_filename, tmpdir)] File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 696, in install_egg return self.egg_distribution(destination) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 661, in egg_distribution metadata = EggMetadata(zipimport.zipimporter(egg_path)) zipimport.ZipImportError: not a Zip file And at this point, I am lost :) cheers, David

2 4

Question re zc.buildout Name Expansion Rules
by Jeff Rush 05 Feb '08

05 Feb '08

In using buildout, I've come across a couple of limitations and I'm wondering if there are workarounds. Suppose I have something like: [FreeTDS_installation] recipe = zc.recipe.cmmi url = blah odbcinst_ini = [FreeTDS] Driver = ${FreeTDS_installation:location}/lib/libtdsodbc.so 1) Since the variable expansion is referring to an attribute of its own .cfg section, is there a way to omit the section name? Something like (but this doesn't work): Driver = ${location}/lib/libtdsodbc.so It just seems extra work to keep putting my own section name in, and is dangerous if I cut/paste lines to move about. 2) The initial case above fails to parse because at the time the ${} expression is reached during read-in time, the part section has not yet been added to the global registry of part sections. Hence I get a "FreeTDS_installation" undefined error. It just seems there ought to be a way for a part section to refer to its own location attribute. Thanks for any tips, -Jeff

2 2

Re: [Distutils] SetupTools on Python 2.5.1 [MSC v.1400 64 bit (AMD64)] on win32 x64
by Phillip J. Eby 05 Feb '08

05 Feb '08

At 09:31 AM 2/4/2008 +0300, Vladimir Kotulskiy wrote: >I there any place where I can read how can I compile setuptools by my self ? Setuptools doesn't need to be compiled, but launcher.c does. The directions are at the top of the file.

1 0

Re: [Distutils] SetupTools on Python 2.5.1 [MSC v.1400 64 bit (AMD64)] on win32 x64
by Phillip J. Eby 04 Feb '08

04 Feb '08

At 02:24 AM 2/2/2008 +0300, Vladimir Kotulskiy wrote: >Hello. >I have installed last setuptools using python ez_setup.py and >have not get any error messages. >When I tried to use easy_install utility I got an error message "Cannot find >Python executable E:\Develop\Python\python.exe". Also I have the >same problem with the Pylons that was installed using ez_setup.py >Is there any way to use easy_install with python for x64 ? > > >Y:\Disk>python >Python 2.5.1 >(<http://pylonshq.com/project/pylonshq/log/?revs=251-54863>r251:54863, >Apr 18 2007, 09:02:36) [MSC v.1400 64 bit (AMD64)] on win32 >Type "help", "copyright", "credits" or "license" for more information. > >Y:\Disk>E:\Develop\Python\python.exe >Python 2.5.1 >(<http://pylonshq.com/project/pylonshq/log/?revs=251-54863>r251:54863, >Apr 18 2007, 09:02:36) [MSC v.1400 64 bit (AMD64)] on win32 >Type "help", "copyright", "credits" or "license" for more information. I'm afraid I don't have an x64 system to test or investigate with. I would guess, however, that the problem has to do with the LoadLibraryEx call in launcher.c: http://svn.python.org/view/sandbox/trunk/setuptools/launcher.c The .exe files compiled from launcher.c are 32-bit, but presumably the python.exe being loaded here is 64-bit, and that is probably causing LoadLibraryEx to fail. Unfortunately, I have no idea how to *fix* it. Perhaps somebody with more Windows/C API experience could chime in here?

1 0

SetupTools on Python 2.5.1 [MSC v.1400 64 bit (AMD64)] on win32 x64
by Vladimir Kotulskiy 02 Feb '08

02 Feb '08

Hello. I have installed last setuptools using python ez_setup.py and have not get any error messages. When I tried to use easy_install utility I got an error message "Cannot find Python executable E:\Develop\Python\python.exe". Also I have the same problem with the Pylons that was installed using ez_setup.py Is there any way to use easy_install with python for x64 ? Y:\Disk>python Python 2.5.1 (r251:54863<http://pylonshq.com/project/pylonshq/log/?revs=251-54863>, Apr 18 2007, 09:02:36) [MSC v.1400 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. Y:\Disk>E:\Develop\Python\python.exe Python 2.5.1 (r251:54863<http://pylonshq.com/project/pylonshq/log/?revs=251-54863>, Apr 18 2007, 09:02:36) [MSC v.1400 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information.

1 0

Setuptools scripts on x64 Windows
by Ian Bicking 02 Feb '08

02 Feb '08

We got a report of problems with Setuptools-generated scripts on x64 Windows XP. I'm pretty sure the problem is in Setuptools: http://pylonshq.com/project/pylonshq/ticket/370 (Submitter is copied) Ian

1 0