Mailman 3 February 2009 - Distutils-SIG

Re: [Distutils] setuptools and shared library dependencies
by P.J. Eby 04 Feb '09

04 Feb '09

At 06:57 AM 2/4/2009 +0100, Greg Landrum wrote: >If I were not using setuputils, I would make sure that I had BASE/bin >in my LD_LIBRARY_PATH and everything would work without problems. > >If I explictly add the bin directory from the egg >(/usr/lib/python2.5/site-packages/BASE-0.1-py2.5-linux-i686.egg) to >LD_LIBRARY_PATH things also work, but requiring this level of >involvement from the user isn't particularly pleasing. > >Is there a solution to this problem or is this a use case that doesn't >fit with setuptools? There's an experimental and unsupported solution, if you use setuptools to build the shared library, and you're on a compatible platform. See the 'tests/shlib_test' subdirectory of the setuptools SVN trunk for info. (The necessary code is in the 0.6 branch as well, but the tests are only in the trunk.) (Also, if you use this approach, the .egg doesn't need to be installed unzipped.)

2 1

setuptools and shared library dependencies
by Greg Landrum 03 Feb '09

03 Feb '09

Dear all, I'm in the process of shifting a project I run over to using setuptools for distribution. Things have mostly worked quite well to this point, so compliments to all involved. :-) I'm just about finished, but I've run up against a problem with extension modules that have shared library dependencies. Here's a schematic of my directory structure: BASE/ bin/ libDepA.so pydir/ __init__.py modA.so foo.py modA.so is an extension module that is dynamically linked against libDepA.so. I've managed to get everything setup so that I can create an egg reproducing the directory structure above, install that egg (not zipped) with easy_install, and do things like >>> from pydir import foo However, when I try to import modA: >>> from pydir import modA I get the (expected) "ImportError: libDepA.so: cannot open shared object file: No such file or directory" If I were not using setuputils, I would make sure that I had BASE/bin in my LD_LIBRARY_PATH and everything would work without problems. If I explictly add the bin directory from the egg (/usr/lib/python2.5/site-packages/BASE-0.1-py2.5-linux-i686.egg) to LD_LIBRARY_PATH things also work, but requiring this level of involvement from the user isn't particularly pleasing. Is there a solution to this problem or is this a use case that doesn't fit with setuptools? thanks, -greg

1 0

GUI for Python package Management
by david.lyon＠preisshare.net 03 Feb '09

03 Feb '09

Hi All, I am a developer from other languages and find myself on python now. I'm wondering if anybody has objections to doing a package management gui for python. My design suggestions would be to: - use WXWidgets (cross compatability for most pythonic platforms) - provide a GUI wrapper for EasyInstall - source packages from http://pypi.python.org/pypi It seems we have most of the componentry in place. The problem seems to be that it doesn't come together in a very user friendly way at the moment that is cohesive. Can anybody/everybody flame/tell me why we shouldn't work to simplify this area of python ?

10 25

[Python Language Summit] Distutils / Packaging survey
by Tarek Ziadé 02 Feb '09

02 Feb '09

Hello A Language Summit will be held in Chicago the day before Pycon. http://us.pycon.org/2009/about/summits/language/ I am preparing a survey to get some feedback from the community before the summit, where I will try to summarize the status, and the possible paths we can take to make things better. The desired output for the summit, will be to have a roadmap for distutils, on actions that meets people' consensus By "community" I mean all the people that have to use Distutils at some point, wether they are installing, developing or packaging for a specific OS, a piece of Python code. I am working on the survey here : http://wiki.python.org/moin/Packaging%20Survey And I need help ! :) If you see weird things, or missing points, please feel free to fix the wiki page and/or discuss it here Thanks Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

21 103

Solaris and distutils: Need to pass LIBDIR explicitly with -L when building extensions?
by Dave Peterson 02 Feb '09

02 Feb '09

I am trying to build a number of projects that use Python extensions on Solaris 10 and I've discovered that nothing with extensions will link unless I explicitly pass in a '-L/path/to/python/lib/dir' because libpython2.5.so is not otherwise found when the '-lpython2.5' argument is specified during linking. This doesn't seem right as I don't have to specify this explicitly on Linux or Windows. Admittedly I'm using a custom built Python, so perhaps I missed some configure argument? Here's my Python build process: ./configure --prefix=/home/dpeterson/py/build --enable-shared make make test make install It is built with the gcc provided by Sun in a default install of Solaris 10, which means the gcc compiler and the sun linker. "gcc -v" gives: Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) If that all seems correct, then it appears the issue is the finalize_options() source in lib/distutils/commands/build_ext.py. There are a number of "if" blocks that explicitly append the value of distutils.sysconfig.get_config_vars('LIBDIR') to the list of library_dirs used to link built extensions with. However, there doesn't seem to be one of these for Solaris / sunos. Is this just an oversite? I've verified that adding a simple block with a 'sunos' value gate solves the problem and I no longer need to be explicit about providing '-L'. Am I missing something or should this patch be submitted as a bugfix on the issue tracker? -- Dave

7 11

[issue58] find_on_path on systems with tight permissions
by Andre Nathan 02 Feb '09

02 Feb '09

New submission from Andre Nathan <andrenth(a)gmail.com>: Hello I'm using setuptools on a server with tight permissions; a normal user is not allowed to list the contents of certain directories, including /usr/bin, which setuptools tries to scan when searching for .egg files. Thus, running any command installed from setuptools fails with OSError: [Errno 13] Permission denied: '/usr/bin' The following change in find_on_path(), in pkg_resources.py, makes it ignore directories which it cannot read: -if os.path.isdir(path_item): +if os.path.isdir(path_item) and os.access(path_item, os.R_OK): Do you think this could be applied? Thanks, Andre ---------- messages: 233 nosy: andrenth priority: bug status: unread title: find_on_path on systems with tight permissions _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue58> _______________________________________________

1 0

Setuptools for Python 3 port ready for testing.
by Lennart Regebro 01 Feb '09

01 Feb '09

I've uploaded an sdist of setuptools ported to Python 3 to here: http://code.google.com/p/python-incompatibility/downloads/list A little more info on my blog: http://regebro.wordpress.com/2009/02/01/setuptools-and-easy_install-for-pyt… -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64

2 1

Uninstall command, the return
by Tarek Ziadé 01 Feb '09

01 Feb '09

Hello Many people are asking for an uninstall command. While there are possible side-effects when removing all installed files, I think it worths it... I would like to introduce an uninstall command in distutils, using Marc-André Lemburg's mxSetup tool (see http://www.egenix.com/products/python/mxBase/) and turning it into a uninstall command. It's quite straighforward since it uses the install command in dry-run mode to get the files to remove. It requires of course to keep the source. Next, (in a second step) I was wondering if a uninstall registery could not be a good thing to have, to store a record of the installed files so there's no need to keep the source for uninstallation. This would required a new command, (and a detailed specification of course) There's an open ticket here about that (#4673) Any thoughts ? Regards Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

7 11