Mailman 3 April 2012 - Distutils-SIG

egg-info & develop
by Andrea Crotti 15 Apr '12

15 Apr '12

I'm trying to understand exactly when running python setup.py develop is necessary to make sure that everything will work as expected. After some thinking I came to the conclusion that all the information that should be kept up-to-date is in the .egg-info directory. So if I understood correctly means that I only need to run "develop" once and "egg_info" every time I need to update. And as a related topic we would really like to avoid cluttering the directories with these egg-info directories, and with my script I know write them in another known directory. But what happens if pkg_resources or similar try to use these information and don't find the egg-info because it's not where it's supposed to be? Thanks, Andrea

2 1

namespace packages broken in ubuntu with zc.buildout 1.5?
by Wichert Akkerman 12 Apr '12

12 Apr '12

I am running into something very odd on an Ubuntu 11.10 system: it looks like namespace packages are entirely broken there. Here is a pdb session to demonstrate: (Pdb) import repoze (Pdb) repoze <module 'repoze' from '/home/wichert/lib/buildout/eggs/repoze.formapi-0.4.2-py2.7.egg/repoze/__init__.pyc'> (Pdb) repoze.__path__ ['/home/wichert/lib/buildout/eggs/repoze.sphinx.autointerface-0.6.2-py2.7.egg/repoze', '/home/wichert/lib/buildout/eggs/repoze.formapi-0.4.2-py2.7.egg/repoze'] So at this point I can import the repoze namespace packages, which is defined by both repoze.sphinx.autointerface and repoze.formapi. Now I try to import repoze.sphinx.autointerface: (Pdb) import repoze.sphinx.autointerface *** ImportError: No module named autointerface That is unexpected since we saw the repoze.sphinx.autointerface egg was found earlier. So lets look at repoze.sphinx: (Pdb) repoze.sphinx <module 'repoze.sphinx' from '/usr/lib/pymodules/python2.7/sphinx/__init__.pyc'> I did not see that coming at all: how can a system sphinx package that is not inside the repoze namespace suddenly appear there? This is especially odd since buildout hooked me up with a sphinx package in the buildout itself: (Pdb) import sphinx <module 'sphinx' from '/home/wichert/lib/buildout/eggs/Sphinx-1.0.1-py2.7.egg/sphinx/__init__.pyc'> I am not sure who is responsible for this behaviour or how to debug this. Does anyone have any useful hints? Wichert.

5 5

Distutils2 Sprint in Montreal
by Éric Araujo 12 Apr '12

12 Apr '12

Hi all, The Montreal-Python user group (http://montrealpython.org/) is hosting a sprint on the 21st of April to work on Distutils2. I will lead the sprint and commit the patches into the main distutils2 and cpython repositories, with the help of a few local hackers. If you live in Montreal, bring your laptop and your enthusiasm, we will provide the food and the good times! No previous knowledge of Distutils2 is required, just general Python skills. Distutils2, as many of you know, is the official successor of Distutils. It aims to be a better, more flexible and more featureful packaging tool for Python authors, as well as a collection of reusable modules implementing the PEPs produced by the distutils-sig third-party packaging tools developers. Everybody loves pip and buildout :) With the first beta versions of Distutils2 and Python 3.3 (which includes Distutils2) coming in June, we are planning a series of sprints to make it ready for prime time. During the sprint, the organization team will guide you through the codebase and provide help and review if you need them. Previous sprints held in Montreal have improved Distutils2, and the participants have had fun and learned things, in line with their motto “For hacks and glory!”. Why don’t you come along for the next one and put your mark on a Python release? The good folks at Radialpoint have graciously provided us with space and free pizza. Come join us on Saturday, the 21st of April, from 12pm to 7pm. The address is: 2050 Bleury Street Suite 300 Map: http://g.co/maps/cuaxc Registration: http://www.eventbrite.ca/event/3261945567 (preferable but not required) Cheers

1 0

Distutils2 Documentation...
by Rob Healey 11 Apr '12

11 Apr '12

Greetings: >From this web page, http://packages.python.org/Distutils2/distutils/setupscript.html, #!/usr/bin/env python from distutils2.core import setup, find_packages setup(name='Distutils2', version='1.0', summary='Python Distribution Utilities', keywords=['packaging', 'distutils2'], author=u'Tarek Ziadé', author_email='tarek(a)ziade.org', home_page='http://bitbucket.org/tarek/distutils2/wiki/Home', license='PSF', packages=find_packages()) Can anyone tell me what I need to do to import setup using Distutils2??? -- Sincerely yours, Rob G. Healey

3 4

Creating a new installation layout
by Tim Cuthbertson 11 Apr '12

11 Apr '12

I'm curious, how would one create a new layout? (as in a --layout=deb alternative). I'd very much like to have a layout that doesn't include any version information in the path, which both "deb" and "unix" do. Ideally, output would look pretty much like: bin/ bin/script1 bin/script2 lib/ lib/some_c_ext.so lib/python/ lib/python/packagename/ lib/python/packagename/__init__.py lib/python/packagename/core.py Something simple, without the unnecessary layers of "usr", "local", "site-packages", "python2.7" etc. The purpose is to be put into a self-contained archive, so it's completely unnecessary to include such namespacing (it will never be mixed in with any other files). Is this possible? not worth it? Right now to achieve at least version independence on the paths I'm running : python setup.py install --root="$DISTDIR" --single-version-externally-managed --install-layout=deb && \ mv "$DISTDIR/usr/lib/"python* "$DISTDIR/usr/lib/python" which is hacky, but works. And you end up with paths like "usr/lib/python/dist-packages" inside the archive, which is just unnecessarily nested for a standalone archive.

2 3

Fwd: specify manifest template other than MANIFEST.in
by kgk 10 Apr '12

10 Apr '12

On Tue, Mar 20, 2012 at 7:22 PM, Éric Araujo <merwok(a)netwok.org> wrote: > Hi, > > Le 20/03/2012 15:10, kgk a écrit : >> The docs seems to suggest you can override the default name MANIFEST.in, > Correct. I tried finding which part of the doc hinted about that to see > if I could improve it and could not find it! Do you have the link? http://docs.python.org/distutils/sourcedist.html#manifest-related-options >> however, I cannot seem to find an option or parameter to do so. > Manifests and manifests templates are only used by the sdist command. > If you run “python setup.py sdist -h”, you’ll find the --template/-t option. I am trying to run sdist throught distrubute or setuptools, I didn';t see that options. In fact, 'sdist -h' was the first thing I tried. I will try with stock distutils and see if it is there. > MANIFEST and MANIFEST.in can’t be found from the index pages in the > Python docs; I will fix that. > Thanks, -- Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599 -- Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599

3 2

questions re: data files with Distribute's test
by Chris Jerdonek 09 Apr '12

09 Apr '12

I have a few questions about including data files when running python setup.py test with Distribute while using Python 3 and the "use_2to3" keyword argument. Some of my test files are in a subdirectory of my project outside of the package directory. I'm able to have the test files copied over to the build directory when running "test" by including a package_data argument something like the following: package_data = {'package': ['../path/to/test/data/*.json']} My questions are-- (1) Is it acceptable to be using parent directories to reference files outside the package directory, or is there a better way to reference paths relative to the project root? Perhaps data_files? (2) Is there an easy way to make it so that these data files get copied only when the test command is being run? The files aren't needed when not developing. (3) Are there any best practices around including/installing test files in distributions (or should they be left out)? Thanks, --Chris

1 0

Can't count on -S to get a clean Python (at least on mac)
by Jim Fulton 08 Apr '12

08 Apr '12

On my mac (Snow Leopard): $ which python /usr/bin/python $ python -S Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin >>> import setuptools >>> setuptools.__file__ '/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/setuptools/__init__.pyc' >>> import os >>> os.listdir('/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python') ['altgraph', 'altgraph-0.6.8.dev-py2.6.egg-info', 'bdist_mpkg', 'bdist_mpkg-0.4.3.dev-py2.6.egg-info', 'bonjour', 'bonjour_py-0.3-py2.6.egg-info', 'CoreGraphics', 'dateutil', 'easy_install.py', 'easy_install.pyc', 'ez_setup', 'fetchmailconf.py', 'fetchmailconf.pyc', 'fetchmailconf.pyo', 'libsvn', 'macholib', 'macholib-1.2.1.dev-py2.6.egg-info', 'modulegraph', 'modulegraph-0.7.2.dev-py2.6.egg-info', 'numpy', 'numpy-1.2.1-py2.6.egg-info', 'OpenSSL', 'pkg_resources.py', 'pkg_resources.pyc', 'py2app', 'py2app-0.4.2-py2.6.egg-info', 'PyObjC', 'PyObjC.pth', 'pyOpenSSL-0.7-py2.6.egg-info', 'PyRSS2Gen-1.0.0-py2.6.egg-info', 'PyRSS2Gen.py', 'PyRSS2Gen.pyc', 'python_dateutil-1.2-py2.6.egg-info', 'setuptools', 'setuptools-0.6c9-py2.6.egg-info', 'site.py', 'site.pyc', 'site.pyo', 'svn', 'twisted', 'Twisted-8.2.0-py2.6.egg-info', 'wx-2.8-mac-unicode', 'wx.pth', 'wxaddons', 'wxaddons-2.8.8.1-py2.6.egg-info', 'wxPython_common-2.8.8.1-py2.6.egg-info', 'wxversion.py', 'wxversion.pyc', 'xattr', 'xattr-0.5-py2.6.egg-info', 'zope', 'zope.interface-3.5.1-py2.6.egg-info'] whimper I get something similar on a Lion machine. I haven't been able to reproduce this lamosity on any linux systems. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://www.dublinstore.com/

3 3

Buildout development list
by Jim Fulton 07 Apr '12

07 Apr '12

So as not to spam people here, I've created a separate list for people working on buildout: https://groups.google.com/forum/?fromgroups#!forum/buildout-development Anyone who want to help with buildout development is welcome. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://www.dublinstore.com/

1 0

zc.buildout: KeyError during "buildout init" with distribute 0.6.25
by Felix Schwarz 07 Apr '12

07 Apr '12

Hey, I use Python 2.7 (Fedora 16). However zc.buildout (1.5.2) does not work for me: $ buildout init Creating '/home/fs/temp/buildout.cfg'. Creating directory '/home/fs/temp/bin'. Creating directory '/home/fs/temp/parts'. Creating directory '/home/fs/temp/eggs'. Creating directory '/home/fs/temp/develop-eggs'. Getting distribution for 'distribute'. Traceback (most recent call last): ... add_activation_listener(lambda dist: dist.activate()) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2230, in activate map(declare_namespace, self._get_metadata('namespace_packages.txt')) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1815, in declare_namespace path = sys.modules[parent].__path__ KeyError: 'peak' An error occurred when trying to install distribute 0.6.25. Look above this message for any errors that were output by easy_install. While: Bootstrapping. Getting distribution for 'distribute'. Error: Couldn't install: distribute 0.6.25 The code which causes the exception is: def declare_namespace(packageName): ... if '.' in packageName: parent = '.'.join(packageName.split('.')[:-1]) declare_namespace(parent) if parent not in _namespace_packages: __import__(parent) try: path = sys.modules[parent].__path__ except AttributeError: raise TypeError("Not a package:", parent) The package which triggers the bug is 'decoratortools' (python package 'peak.utils'). If I install other namespace packages (e.g. zope.interface) everything works fine. The error happens because 'peak' is not in sys.modules when buildout calls it's easy_install implementation. If I add some code to ignore the keyerror, everything works as expected though I'm not sure that this is the right fix. Any idea how I can fix this? Pointers welcome. fs

1 3