Mailman 3 August 2012 - Distutils-SIG

Can I have distribute build a file for me?
by Ken Kundert 09 Aug '12

09 Aug '12

Currently I am use an import in my setup script to build a file I need during the install. Specifically: #!/usr/bin/env python import distribute_setup distribute_setup.use_setuptools() from setuptools import setup import manpage # simply importing manpage creates the ec.1 as a side effect setup( name='ec', version='1.0', ..., data_files=[('man/man1', ['ec.1'])], ... ) However, I require that docutils be installed in advance otherwise the import will fail. To resolve this, I would like to use setup_requires='docutils>0.7'. For this to be effective, I will have to arrange things so that the import occurs during the evaluation of setup(). Is that possible? I have created an ugly hack that works by calling setup() twice ... setup( name='ec', version='1.0', ..., setup_requires='docutils >= 0.7', ...) import manpage # simply importing manpage creates the ec.1 as a side effect setup( name='ec', version='1.0', ..., data_files=[('man/man1', ['ec.1'])], ...) But I cannot help but believe there must be a better way. Is there some way add a hook to setup to get it to do the import for me after setup_requires has been processed? If not, is there some way to install docutils if needed before I call setup()? -Ken

2 3

PEP proposal: multi-interpreter naming convention for built distributions
by Daniel Holth 08 Aug '12

08 Aug '12

I propose a three-part Implementation, ABI, Architecture naming scheme for built distributions as a new Python standard. The full list of allowed tags would need to be fleshed out for this to be completed, but I don't know enough about the needs of each implementation. https://bitbucket.org/dholth/python-peps/src/tip/pep-CTAG.txt Summary Built distributions need a file naming scheme that indicates the Python implementation, the ABI, and the platform. Today pypy and CPython's "setup.py bdist" generate the same filename but incompatible bdists. This is a problem if you would like to share the two bdists in the same folder. Instead, they should generate distinct bdist filenames because one won't work with the other implementation. This PEP only specifies a tagging system that could be used in bdist filenames. This mostly considers the needs of CPython. I hope to get input from the other implementation communities, or in fact anyone at all. Thanks, Daniel Holth

2 2

[ANNOUNCE] pypiserver 0.6.1 - minimal private pypi server
by Ralf Schmitt 07 Aug '12

07 Aug '12

Hi, I've just uploaded pypiserver 0.6.1 to the python package index. pypiserver is a minimal PyPI compatible server. It can be used to serve a set of packages and eggs to easy_install or pip. pypiserver is easy to install (i.e. just easy_install pypiserver). It doesn't have any external dependencies. http://pypi.python.org/pypi/pypiserver/ should contain enough information to easily get you started running your own PyPI server in a few minutes. The code is available on github: https://github.com/schmir/pypiserver Changes in version 0.6.1 ------------------------ - make 'python setup.py register' work - added init scripts to start pypiserver on ubuntu/opensuse -- Cheers Ralf

1 0

[issue143] Cannot install: ValueError: bad marshal data (unknown type code)
by Valentin Lorentz 05 Aug '12

05 Aug '12

New submission from Valentin Lorentz: Hi, I cannot use setuptools with use_2to3=True. The traceback as attachment, and here is my setup.py: http://paste.progval.net/show/93/ (I cannot add another attachment) fixes_2to3 is a directory containing fixes and this __init__.py : from . import fix_def_iteritems, fix_def_itervalues, fix_def_iterkeys, fix_reload from lib2to3.fixes import * I use setuptools 0.6.24-1 from Debian GNU/Linux Sid, with Python 3.2.3-4. Regards, Valentin ---------- files: setuptools_traceback.txt messages: 690 nosy: ProgVal priority: bug status: unread title: Cannot install: ValueError: bad marshal data (unknown type code) Added file: http://bugs.python.org/setuptools/file87/setuptools_traceback.txt _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue143> _______________________________________________

1 0