Distutils-SIG May 2010

distutils-sig@python.org

46 participants
72 discussions

Re: [Distutils] Having a Python package install itself under a different name
by P.J. Eby 27 May '10

27 May '10

At 10:40 PM 5/27/2010 +0200, cool-RR wrote: >Is there a way that `garlicsim_py3` will install itself under the >alias `garlicsim`? What I want is for a Python 3 user to be able to >`import garlicsim` and refer to the module all the time as >`garlicsim`, but that it will really be `garlicsim_py3`. Why not just develop them both with the same package name? Your project name (in setup(name='...')) can still be different.

2 1

virtualenv python3 port
by Sridhar Ratnakumar 27 May '10

27 May '10

I would like to help with virtualenv Python 3 port. http://bitbucket.org/brandon/virtualenv3/ seems to be outdated (not in sync with core) and thus buggy. Does not even actually use Distribute as claimed. Brandon, would you be interested in merging and making a release if I provide a patch? Should I work on a separate branch or directly on yours? I intend to sync with the core, retaining 2to3 changes. -srid

2 1

"Out of source" bdist_egg, missing metadata
by Augusto Destrero 27 May '10

27 May '10

Hi, sorry if this email arrives twice. Now I'm registered to this list, so I can check that the email is delivered. :) I've a question on setuptools egg creation. I've a directory structure like this: python_libs/ |---- setup_foo | |---- setup.py |---- src | |---- foo | | |---- __init__.py | | |---- foo_module.py | |---- bar | | |---- __init__.py | | |---- bar_module.py | |---- common | | |---- __init__.py | | |---- common_module.py Basically I have a src directory containing three packages (foo, bar and common), and I have a setup_foo directory OUTSIDE src, where I want to build an egg containing foo and common packages, and NOT bar package. In the setup_foo/setup.py script I have something like this: # -*- coding: utf-8 -*- from setuptools import setup, find_packages src_dir = "../src" setup(name='foo', version='0.1', description="foo and common packages", packages=find_packages(src_dir, exclude=['bar', 'bar.*']), package_dir={'': src_dir}, zip_safe=False, install_requires=[ 'PasteDeploy', ], entry_points=""" [paste.app_factory] foo_app = foo.foo_module:app_factory common_app = common.common_module:app_factory """, ) You can see that I have two entry points (in this case for use with PasteDeploy in a wsgi project). If I build an egg with that file: $ cd setup_foo/ $ python setup.py bdist_egg I can find a foo.egg-info directory under src which contains all metadata: $ ls src/foo.egg-info/ dependency_links.txt entry_points.txt not-zip-safe PKG-INFO requires.txt SOURCES.txt top_level.txt But in the egg created under setup_foo/dist I don't have those metadata: $ cd setup_foo/dist/ $ unzip foo-0.1-py2.6.egg $ ls EGG-INFO/ not-zip-safe SOURCES.txt And of course, after installing that egg with easy_install, PasteDeploy can't find the entry points. Is this a setuptools bug or I'm doing something wrong? I use setuptools 0.6.10 distributed in Ubuntu Lucid. Thank you in advance for your help, and excuse me for the lenghty email! -- Augusto Destrero

2 2

"Out of source" bdist_egg, missing metadata
by Augusto Destrero 27 May '10

27 May '10

Hi, I've a question on setuptools egg creation. I've a directory structure like this: python_libs/ |---- setup_foo | |---- setup.py |---- src | |---- foo | | |---- __init__.py | | |---- foo_module.py | |---- bar | | |---- __init__.py | | |---- bar_module.py | |---- common | | |---- __init__.py | | |---- common_module.py Basically I have a src directory containing three packages (foo, bar and common), and I have a setup_foo directory OUTSIDE src, where I want to build an egg containing foo and common packages, and NOT bar package. In the setup_foo/setup.py script I have something like this: # -*- coding: utf-8 -*- from setuptools import setup, find_packages src_dir = "../src" setup(name='foo', version='0.1', description="foo and common packages", packages=find_packages(src_dir, exclude=['bar', 'bar.*']), package_dir={'': src_dir}, zip_safe=False, install_requires=[ 'PasteDeploy', ], entry_points=""" [paste.app_factory] foo_app = foo.foo_module:app_factory common_app = common.common_module:app_factory """, ) You can see that I have two entry points (in this case for use with PasteDeploy in a wsgi project). If I build an egg with that file: $ cd setup_foo/ $ python setup.py bdist_egg I can find a foo.egg-info directory under src which contains all metadata: $ ls src/foo.egg-info/ dependency_links.txt entry_points.txt not-zip-safe PKG-INFO requires.txt SOURCES.txt top_level.txt But in the egg created under setup_foo/dist I don't have those metadata: $ cd setup_foo/dist/ $ unzip foo-0.1-py2.6.egg $ ls EGG-INFO/ not-zip-safe SOURCES.txt And of course, after installing that egg with easy_install, PasteDeploy can't find the entry points. Is this a setuptools bug or I'm doing something wrong? I use setuptools 0.6.10 distributed in Ubuntu Lucid. Thank you in advance for your help, and excuse me for the lenghty email! Please answer also to my email address, because I'm not a list subscriber. -- Augusto Destrero

1 0

on storing vcs version infos in sdists
by Ronny Pfannschmidt 25 May '10

25 May '10

hi, whats a good place to store version information from a vcs in a sdist, without needing to drop them into python files. i wrote a simple module that gets me version meta-data from hg repos/archives, using the same algorithms hg is using for its own version number generation. The nit in that is that i have to store it in a python file. I'd much rather put it somewhere else in case of sdists, but i have no idea where/how i should put it to fit with the setuptools/distribute standards. -- Ronny

3 3

Script for easy access to the coverage report on distutils2
by Yannick Gingras 25 May '10

25 May '10

Greetings Packagers, as part of our sprinting effort at Montréal-Python, we found it relevant to give an easy access to the test coverage reports to sprinters because it really helps them to see what needs more testing and when kind of breakage then can expect the tests to catch. I tried to use nose but the naming convention used seem to trigger way too many false positives so I'm afraid that we have to rule distutils2 as nose-incompatible. I could add a series of commands to our wiki, which is good for us but not very helpful to other distutils2 hackers, or I could integrate coverage in the current `runtests.py` test runner. Is there anyone one against adding a --with coverage option to `runtests.py`? Cheers, -- Yannick Gingras http://ygingras.net http://montrealpython.org -- lead organizer

3 5

development egg and --find-links easy_install option
by Manlio Perillo 23 May '10

23 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. Reading easy_install documentation I recently discovered the - --find-links option, and I'm starting to experiment with it in order to create a tar archive with all the dependencies of a Python package. This is very useful when I have to deploy a package on a shared hosting, where can be a problem to compile extension modules. Unfortunately in my setup I use some packages (the main package being installed and one of its install requirements) in "develop" mode. These packages, moreover, are not available on PyPi. To summarize, I have a package A (to be installed in develop mode), that depends on package B, installed in develop mode. B, then, have additional install requirements, as "normal" packages. A have additional install requirements, as "normal" packages. When I run, from A source directory, the command: python setup.py develop -maxd deps/ an A.egg-link file is correctly copied to the `deps` directory. However, when processing B package, I get: Skipping development or system egg: B 0.1dev Reading http://pypi.python.org/simple/B/ ... Using the `-H none` option, will skip processing of B package and additional dependencies (including direct A dependencies). What is the reason why a development egg is being skipped? What I want is that in `deps` directory should copied all "normal" packages, as eggs, that are install requirements for package A or, indirectly, package B. Is this possible? Thanks Manlio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv3/mQACgkQscQJ24LbaUSpbACfcp0gFJhxtlZpjR5D5XQg7q8J FKwAn1ddZhdzQorR+CxGSt30sW+qRKuW =pJ0V -----END PGP SIGNATURE-----

2 6

Distribute 0.6.12 broken on Windows
by Sridhar Ratnakumar 21 May '10

21 May '10

May I call your attention to this bug? http://bitbucket.org/tarek/distribute/issue/151/ 0.6.12 broke Windows installation. Are we not planning a new release? -srid

3 12

2.6 replacement for sysconfig.get_paths(scheme)[path]?
by Sridhar Ratnakumar 20 May '10

20 May '10

Python 2.7 introduced the `sysconfig` module which has a function `get_paths` that returns the fully variable substituted path for the given scheme. This doesn't seem like possible on 2.6 using `distutils.sysconfig` - as variable substitution is done deep in a class method, and not exposed as a public API. At the moment I am writing code like this: scheme = 'nt' sys.platform == 'win32' else 'unix' scheme += ('_user' if usersite else ( '_prefix' if scheme == 'unix' else '')) template = INSTALL_SCHEMES[scheme][path] # hardcoded template substitution (distutils API does not provide # this) template = template.replace('$base', base_dir) template = template.replace('$py_version_short', pyver) if '$user' in template: template = template.replace('$usersite', site.USER_SITE) template = template.replace('$userbase', site.USER_BASE) assert '$' not in template, \ 'Unsubstituded variables left in "%s"' % template return template Can this be simplified? -srid

1 0

pypi.python.org as single point of failure
by Tom Gross 18 May '10

18 May '10

Hello together, because of the breakdown of pypi.python.org I found that this Python index is hardcoded in the distribute_setup.py-script. I tried to workaround the breakage of the index-server by changing my hosts-file pointing to a pypi-mirror found on http://www.coactivate.org/projects/pypi-mirroring/project-home, but the directory structure is different there, so it didn't work. I ran into this problem first by using the bootstrap-command of zc.buildout. this is probably the wrong list to discuss this, but I think it should be possible to *fully* replace pypi by a mirror for all setuptools, distribute, zc.buildout-variants by configuration. Cheers, -Tom

2 2

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Distutils-SIG May 2010