Mailman 3 November 2009 - Distutils-SIG

Re: [Distutils] new metadata fields to aid PyPI...
by Chris Withers Nov. 25, 2009

Nov. 25, 2009

Tarek Ziadé wrote: > Note that I have introduced three new fields in PEP 345 to help on this (after > I have read Catalog-SIG threads on the commenting issues -- someone > suggested them): > > http://www.python.org/dev/peps/pep-0345 > > # Repository-URL > # Repository-Browser-URL > # Bug-Tracker-URL I wonder use Repository-Browser-URL but I would like to see: Documentation-URL MailingList-URL ChangeLog-URL cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

1 0

specifying the shipping of subpackages without their superpackages
by Ronny Pfannschmidt Nov. 25, 2009

Nov. 25, 2009

Hi, i recently noticed that shipping a package like 'foo.bar' without also shipping 'foo' seems to work fine in distutils. since that would be nice way to ship packages within a namespace i want to sugest specifying the fact that it works and to clarify how it works. Regards Ronny

3 3

Buildout and PIL problem
by Restless Being Nov. 23, 2009

Nov. 23, 2009

Hi all! I have a virtualenv created with --no-site-packages option and I'm going to install there Django and some required libs using buildout. The problematic library is PIL. Here is my buildout.cfg [buildout] parts = PIL django [django] recipe = djangorecipe version = 1.1 project = project eggs = psycopg2 PIL south django-reversion django-cms wsgi = true settings = production [PIL] recipe = zc.recipe.egg:custom egg = PIL==1.1.6 find-links = http://dist.repoze.org and it is something generally recommended by other users. See: http://www.stereoplex.com/two-voices/a-django-development-environment-with-… I also tried some other versions of [PIL] like: [PIL] recipe = zc.recipe.egg:custom egg = PIL==1.1.6 find-links = http://dist.repoze.org/PIL-1.1.6.tar.gz index = http://dist.repoze.org/index The first problem is that the above recipe installs PIL 1.1.7 instead of 1.1.6. Here is install log: python bin/buildout -c devel.cfg Updating django. Getting distribution for 'PIL'. WARNING: '' not a valid package name; please use only.-separated package names in setup.py In file included from /usr/include/python2.6/Python.h:8, from libImaging/ImPlatform.h:10, from libImaging/Imaging.h:14, from Tk/tkImaging.c:53: /usr/include/python2.6/pyconfig.h:1028:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/stdio.h:28, from /usr/include/tcl.h:141, from /usr/include/tk.h:21, from Tk/tkImaging.c:51: /usr/include/features.h:210:1: warning: this is the location of the previous definition -------------------------------------------------------------------- PIL 1.1.7 SETUP SUMMARY -------------------------------------------------------------------- version 1.1.7 platform linux2 2.6.4 (r264:75706, Oct 27 2009, 06:16:59) [GCC 4.4.1] -------------------------------------------------------------------- --- TKINTER support available --- JPEG support available --- ZLIB (PNG/ZIP) support available --- FREETYPE2 support available --- LITTLECMS support available -------------------------------------------------------------------- To check the build, run the selftest.py script. zip_safe flag not set; analyzing archive contents... Image: module references __file__ Got PIL 1.1.7. Second problem is that the above PIL installation doesn't work with Django: bin/django validate Error: One or more models did not validate: picture.picture: "image": To use ImageFields, you need to install the Python Imaging Library. Get it at http://www.pythonware.com/products/pil/ . At the same time, everything is ok when I manually install PIL using: pip install http://effbot.org/downloads/Imaging-1.1.6.tar.gz Any hints? Jakub

3 5

Buildout and PIL problem
by Restless Being Nov. 23, 2009

Nov. 23, 2009

Hi! I have a virtualenv created with --no-site-packages option and I'm going to install there Django and some required libs using buildout. The problematic library is PIL. Here is my buildout.cfg [buildout] parts = PIL django [django] recipe = djangorecipe version = 1.1 project = project eggs = psycopg2 PIL south django-reversion django-cms wsgi = true settings = production [PIL] recipe = zc.recipe.egg:custom egg = PIL==1.1.6 find-links = http://dist.repoze.org and it is something generally recommended by other users. See: http://www.stereoplex.com/two-voices/a-django-development-environment-with-… I also tried some other versions of [PIL] like: [PIL] recipe = zc.recipe.egg:custom egg = PIL==1.1.6 find-links = http://dist.repoze.org/PIL-1.1.6.tar.gz index = http://dist.repoze.org/index The first problem is that the above recipe installs PIL 1.1.7 instead of 1.1.6. Here is install log: python bin/buildout -c devel.cfg Updating django. Getting distribution for 'PIL'. WARNING: '' not a valid package name; please use only.-separated package names in setup.py In file included from /usr/include/python2.6/Python.h:8, from libImaging/ImPlatform.h:10, from libImaging/Imaging.h:14, from Tk/tkImaging.c:53: /usr/include/python2.6/pyconfig.h:1028:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/stdio.h:28, from /usr/include/tcl.h:141, from /usr/include/tk.h:21, from Tk/tkImaging.c:51: /usr/include/features.h:210:1: warning: this is the location of the previous definition -------------------------------------------------------------------- PIL 1.1.7 SETUP SUMMARY -------------------------------------------------------------------- version 1.1.7 platform linux2 2.6.4 (r264:75706, Oct 27 2009, 06:16:59) [GCC 4.4.1] -------------------------------------------------------------------- --- TKINTER support available --- JPEG support available --- ZLIB (PNG/ZIP) support available --- FREETYPE2 support available --- LITTLECMS support available -------------------------------------------------------------------- To check the build, run the selftest.py script. zip_safe flag not set; analyzing archive contents... Image: module references __file__ Got PIL 1.1.7. Second problem is that the above PIL installation doesn't work with Django: bin/django validate Error: One or more models did not validate: picture.picture: "image": To use ImageFields, you need to install the Python Imaging Library. Get it at http://www.pythonware.com/products/pil/ . At the same time, everything is ok when I manually install PIL using: pip install http://effbot.org/downloads/Imaging-1.1.6.tar.gz Any hints? Jakub

1 0

One package for both python and jython
by Fabrizio Pollastri Nov. 20, 2009

Nov. 20, 2009

Hello, I am trying to upgrade a pure python package distribution based on distutils in such a way that it will work with both python and jython. Since my package depends on some part of python library when run by python and on some other part of jython library when run by jython, the source structure is the following. my_package_source_dir/ common_files files_for_python files_for_jython It will be a maximum, if distutils let me to reach the following goals. 1. python/jython setup.py sdist command has to build the distribution tar my_package.tar.gz containing all files required by python and by jython. 2. python setup.py install command has to install in the python package tree my_package_source_dir/ common_files files_for_python 3. jython setup.py install command has to install in the jython package tree my_package_source_dir/ common_files files_for_jython It is possible to implement this behavior with the setup function of distutils? There are other ways (please, no package split)? Any suggestion is welcome. Thank you in advance. Fabrizio Pollastri

2 1

distribute traceback
by Neal Becker Nov. 19, 2009

Nov. 19, 2009

sudo easy_install -U openopt Processing openopt Running OOPy/setup.py -q bdist_egg --dist-dir /home/nbecker/openopt/OOPy/egg-dist-tmp-fTMbRS Adding openopt 0.24.dev to easy-install.pth file Installed /usr/lib/python2.6/site-packages/openopt-0.24.dev-py2.6.egg Processing dependencies for openopt==0.24.dev Finished processing dependencies for openopt==0.24.dev Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/lib64/python2.6/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib64/python2.6/multiprocessing/util.py", line 258, in _exit_function info('process shutting down') TypeError: 'NoneType' object is not callable Error in sys.exitfunc: Traceback (most recent call last): File "/usr/lib64/python2.6/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib64/python2.6/multiprocessing/util.py", line 258, in _exit_function info('process shutting down') TypeError: 'NoneType' object is not callable At least, I think it's distribute (I just did update fedora 11->12, so maybe something got screwed up). I did easy_install -U distribute after the update. sudo easy_install -U distribute Searching for distribute Reading http://pypi.python.org/simple/distribute/ Reading http://packages.python.org/distribute Best match: distribute 0.6.8 Processing distribute-0.6.8-py2.6.egg distribute 0.6.8 is already the active version in easy-install.pth Installing easy_install script to /usr/bin Installing easy_install-2.6 script to /usr/bin Using /usr/lib/python2.6/site-packages/distribute-0.6.8-py2.6.egg Processing dependencies for distribute Finished processing dependencies for distribute

4 14

obtaining easy_install prefix in setup.py
by Pavol Juhas Nov. 19, 2009

Nov. 19, 2009

Hello, I searched and read the recent discussions on the distutils-sig list and I hope someone can help me with the following problem. Is there a way to recover the prefix value inside pkgfoo/setup.py, when it is installed as easy_install --prefix=value pkgfoo (pkgfoo is a directory with setup.py) I can get the prefix, when pkgfoo is installed with python setup.py install --prefix=value by overloading the bdist_egg class and passing it via cmdclass argument to the setup function: http://danse.us/trac/diffraction/browser/diffraction/diffpy.lib/trunk/setup… http://danse.us/trac/diffraction/browser/diffraction/diffpy.lib/trunk/setup… However, this does not work under easy_install, because easy_install already creates its own distribution object before sourcing pkgfoo/setup.py, in addition setup.py is executed in a sandbox with mangled sys.argv. Has anybody, perhaps David Cournapeau, figured out how to wrestle the prefix value out of easy_install? Thank you all, Pavol PS: Let me give you some background for what I am trying to do. I am working on several Python packages that need to be distributed together with a shared C++ library (libdiffpy.so). So far I have used scons to build and install the library and that has been working really well. However, I would like to have a dependency resolution for any client packages as available in the setuptools. After wading through the "People want CPAN" thread I realized that converting my scons scripts to distutils would be a hopeless task. So my solution is to package the library sources in a phony python package diffpy.lib, where its setup.py is extended to execute scons that actually takes care of the library build and installation. I have decided to ignore all setup.py options and take care of the prefix under which the library should be installed. However to do so, I need to recover the prefix value and pass it to scons.

5 6

[issue97] Windows installer causes different behavior
by David Hart Nov. 18, 2009

Nov. 18, 2009

New submission from David Hart <dbhart(a)sandia.gov>: Using the windows .exe installer for setuptools0.6c11 causes an error that is not present when using the .tar.gz and installing from source (python setup.py install). easy_install.exe behaves differently between the two methods. Using the .exe, you can no longer download the setuptools package (see attached) - it finds it somewhere cached, and then tries to overwrite itself. Using the .tar.gz build, it behaves correctly. ---------- messages: 467 nosy: dbhart priority: bug status: unread title: Windows installer causes different behavior _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue97> _______________________________________________

1 0

PEP 345 update + RFC on "Requires-External" and "Requires-Python"
by Tarek Ziadé Nov. 18, 2009

Nov. 18, 2009

Hello I've update PEP 345 with a first draft about the markers, http://python.org/dev/peps/pep-0345/#environment-markers PEP 390 is being reworked accordingly, but I guess we can have a new round of comments on PEP 345 and PEP 386, as they can be accepted and added in Python independently from the other PEPs. There's also a "Requires-External" field that was added in the first update of 345, that we need to discuss. The idea of this field is to be able to define a non-Python dependency in the metadata. It's based on a list stored and managed at PyPI. Values could be things like "libxslt", "libpng", etc.. Last, "Requires-Python" is introduced to define the version of Python. I am not sure this is required anymore since Martin has added a Trove classifier for this. But in the meantime, this is stronger than a "simple" classifier I think. Any comments ? Regards Tarek -- Tarek Ziadé | http://ziade.org | オープンソースはすごい! | 开源传万世，因有你参与

11 35

Re: [Distutils] PEP 345 update + RFC on "Requires-External" and "Requires-Python"
by Tres Seaver Nov. 17, 2009

Nov. 17, 2009

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tarek Ziadé wrote: > On Tue, Nov 17, 2009 at 10:28 PM, Tres Seaver <tseaver(a)palladion.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Tarek Ziadé wrote: >> >>> That's why I said that 100% of the information could stay in PKG-INFO >>> (==the metadata), >>> instead of having to maintain something else at PyPI. >> Apoligies for misunderstanding: I thought you were arguing to remove >> the field from PKG-INFO. I'm fine with removing any mandate for a >> registry from the PEP. > > That's fine, probably related to my frenglish too. > > There's one thing though: do we want the url and description data with > the name ? I would say we don't need anything. This field is like the "data type" stuff (not yet in a PEP): we want the downstream folks from Fedora / Debian to suggest values to the upstream (PyPI) package maintainer. I think we can get "enough" traction from just having a well-understood name ('zlib', 'libxslt', etc.) in this field. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksDHUkACgkQ+gerLs4ltQ5PbQCeOV980LniLELp1PROe8Vyyh1u bEkAoMv135Mhk/V4w8u1Og++JJNbUr56 =v5Kr -----END PGP SIGNATURE-----

1 0