Mailman 3 March 2012 - Distutils-SIG

Re: [Distutils] distutils2 1.0a4 and simple package
by kgk March 22, 2012

March 22, 2012

Thanks for the pointer, is there anyway to use another filename other than setup.cfg? I am trying to build several related package from a common root? On Wed, Mar 21, 2012 at 1:57 PM, Thibault Kruse <tkruse(a)willowgarage.com> wrote: > Seems that docu is outdated, as far as I understand the future of disutils2 > is in the setup.cfg instead of a setup.py: > > http://docs.python.org/dev/packaging/setupcfg.html > > though that doc could probably still be improved a bit. > > > On Wed, Mar 21, 2012 at 1:22 PM, kgk <kkvilekval(a)gmail.com> wrote: >> >> I am trying distutils2 cannot get anything to start.. The doc[1] and [2] >> suggest that one should simply >> >> from distutils2.core import setup >> >> >> However, this does not seem to work anymore. >> Is there a newer way, or is it a bug? >> >> Thanks >> >> >> [1] http://docs.python.org/dev/packaging/ >> [2]http://packages.python.org/Distutils2/distutils/setupscript.html >> >> -- >> Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599 >> _______________________________________________ >> Distutils-SIG maillist - Distutils-SIG(a)python.org >> http://mail.python.org/mailman/listinfo/distutils-sig > > -- Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599

5 4

pip installing to system packages
by John Anderson March 22, 2012

March 22, 2012

I activate my virtualenv, then try to use pip and it tries to install to the system packages: [koru-sontek.rhcloud.com ~]\> source ~/koru/virtenv/bin/activate (virtenv)[koru-sontek.rhcloud.com ~]\> which pip /var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/bin/pip (virtenv)[koru-sontek.rhcloud.com ~]\> which python /var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/bin/python (virtenv)[koru-sontek.rhcloud.com ~]\> pip install sqlalchemy Downloading/unpacking sqlalchemy Running setup.py egg_info for package sqlalchemy warning: no files found matching '*.jpg' under directory 'doc' no previously-included directories found matching 'doc/build/output' Installing collected packages: sqlalchemy Running setup.py install for sqlalchemy error: could not create '/usr/lib64/python2.6/site-packages/sqlalchemy': Permission denied Complete output from command /usr/bin/python2.6 -c "import setuptools;__file__='/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/build/sqlalchemy/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-version-externally-managed --record /tmp/pip-xro6j5-record/install-record.txt --install-headers /var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/include/site/python2.6: running install running build running build_py running build_ext running install_lib creating /usr/lib64/python2.6/site-packages/sqlalchemy error: could not create '/usr/lib64/python2.6/site-packages/sqlalchemy': Permission denied ---------------------------------------- Command /usr/bin/python2.6 -c "import setuptools;__file__='/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/build/sqlalchemy/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-version-externally-managed --record /tmp/pip-xro6j5-record/install-record.txt --install-headers /var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/include/site/python2.6 failed with error code 1 Storing complete log in /var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/.pip/pip.log Traceback (most recent call last): File "/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/bin/pip", line 9, in <module> load_entry_point('pip==1.0.2', 'console_scripts', 'pip')() File "/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/__init__.py", line 116, in main return command.main(initial_args, args[1:], options) File "/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/basecommand.py", line 151, in main log_fp = open_logfile(log_fn, 'w') File "/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/koru/virtenv/lib/python2.6/site-packages/pip-1.0.2-py2.6.egg/pip/basecommand.py", line 177, in open_logfile os.makedirs(dirname) File "/usr/lib64/python2.6/os.py", line 157, in makedirs mkdir(name, mode) OSError: [Errno 13] Permission denied: '/var/lib/stickshift/47718763f63148a089bdb31e7ad72d5a/.pip'

1 0

distutils2 1.0a4 and simple package
by kgk March 22, 2012

March 22, 2012

I am trying distutils2 cannot get anything to start.. The doc[1] and [2] suggest that one should simply from distutils2.core import setup However, this does not seem to work anymore. Is there a newer way, or is it a bug? Thanks [1] http://docs.python.org/dev/packaging/ [2]http://packages.python.org/Distutils2/distutils/setupscript.html -- Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599

2 2

bash completion files with easy_install
by Thibault Kruse March 21, 2012

March 21, 2012

Hi, I am confused about how to provide bash completion files for users of a program to be installed via setuptools. I am working with Ubuntu Lucid mainly, and I have a setup.py like this: setup(... data_files=[('/etc/bash_completion.d', ['contrib/mytool.bash'])]) And also a MANIFEST.in with this include contrib/mytool.bash as a workaround for this problem: http://stackoverflow.com/questions/2994396/python-distutils-does-not-includ… Now what happens in Ubuntu Lucid is that easy_install will fail with a SandboxViolation for these files if I easy_install the software. pip install however does not fail. I do not want to force users to use pip, and I am not sure whether easy_install is doing the right thing in using a sandbox. Also i have no idea what will happen on windows machines, where no /etc exists, and no bash exists neither. So can somebody here tell me how I should approach this problem? If anyone wants to reproduce, try this: sudo easy_install -U rosinstall==0.6.9 regards, Thibault

1 0

specify manifest template other than MANIFEST.in
by kgk March 21, 2012

March 21, 2012

I would like to keep several related distributions in a single top level directory. In order to do the proper packaging, each package will need it's own MANIFEST.in The docs seems to suggest you can override the default name MANIFEST.in, however, I cannot seem to find an option or parameter to do so. Thanks for any pointers. Kris -- Kristian G. Kvilekval (kkvilekval(a)gmail.com) 805-636-1599

2 1

Re: [Distutils] setup.py, data_files and i18n
by Bruno Braga March 18, 2012

March 18, 2012

Hei Erik, Thanks… That does the trick! But there is still an issue regarding where the files will be installed. On Ubuntu, it goes to: /usr/local/share/locale and this does not work because gettext looks at: /usr/share/locale On mac (lion), however, it works. The installed failed go to: /System/Library/Frameworks/Python.framework/Versions/2.7/share/locale/ And gettext looks at: /opt/local/share/locale Even though, python seems to pick up the l10n right. The same does not happen in Linux, unless I force the setup.py to install in /usr path… How can I tell python to look for that directory in particular instead of the default? My concern here is that I should not hard-code this path in the gettext.translation() method, which would then not work for other people with non-standard locations, or on mac, or on Windows… I read about setting up m4 alike strings in python code that would be replaced by distutils upon compilation, but I could not find any reference for that, neither if that is a solution for my problem. Thanks for your help. -- Braga, Bruno www.brunobraga.net (http://www.brunobraga.net/) bruno.braga(a)gmail.com (mailto:bruno.braga@gmail.com) On Tuesday, 6 March 2012 at 5:35 AM, Erik Bray wrote: > On Thu, Mar 1, 2012 at 11:02 PM, BRAGA, Bruno <bruno.braga(a)gmail.com (mailto:bruno.braga@gmail.com)> wrote: > > Hi, > > > > I am working on a project written in Python, and I would like to use i18n > > functionality, but I am having some issues with it, more specifically > > regarding the .mo files location, and I was hoping someone here could point > > me in the right direction. > > > > (1) i18n mo files location > > > > Basically, I already know how to translate contents with gettext, but I got > > stuck with the fact that it, by default, looks at > > /usr/share/locale/{language} (in Linux), but the setup.py install data_files > > into /usr/local/share/... unless I forcibly use absolute paths toward the > > location where the files should be. > > > > (2) install_data.data_files > > > > Also, I am having a problem to install the data_files, because the > > install_data command is never called. I made it work before, but I don't > > understand what I am missing that worked before and not now. > > > > Here is the setup.py script: > > https://github.com/brunobraga/termsaver/blob/master/setup.py > > > > And this is the i18n module I am using as base for localizing all text in > > the application: > > https://github.com/brunobraga/termsaver/blob/master/termsaverlib/i18n.py > > > > Here is the output of a clean install: > > > > bruno@development3;~$ sudo python setup.py install --record > > /tmp/termsaver.install.record.txt > > [sudo] password for bruno: > > running install > > running build > > running build_py > > creating build > > creating build/lib.linux-i686-2.7 > > creating build/lib.linux-i686-2.7/termsaverlib > > copying termsaverlib/constants.py -> build/lib.linux-i686-2.7/termsaverlib > > copying termsaverlib/i18n.py -> build/lib.linux-i686-2.7/termsaverlib > > copying termsaverlib/common.py -> build/lib.linux-i686-2.7/termsaverlib > > copying termsaverlib/exception.py -> build/lib.linux-i686-2.7/termsaverlib > > copying termsaverlib/__init__.py -> build/lib.linux-i686-2.7/termsaverlib > > creating build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/programmer.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/rssfeed.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/rfc.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/urlfetcher.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/jokes4all.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/dot.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/__init__.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/asciiartfarts.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/quotes4all.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > copying termsaverlib/screen/randtxt.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen > > creating build/lib.linux-i686-2.7/termsaverlib/screen/base > > copying termsaverlib/screen/base/rssfeed.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/base > > copying termsaverlib/screen/base/urlfetcher.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/base > > copying termsaverlib/screen/base/filereader.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/base > > copying termsaverlib/screen/base/__init__.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/base > > creating build/lib.linux-i686-2.7/termsaverlib/screen/helper > > copying termsaverlib/screen/helper/position.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/helper > > copying termsaverlib/screen/helper/urlfetcher.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/helper > > copying termsaverlib/screen/helper/typing.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/helper > > copying termsaverlib/screen/helper/xmlreader.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/helper > > copying termsaverlib/screen/helper/__init__.py -> > > build/lib.linux-i686-2.7/termsaverlib/screen/helper > > running build_scripts > > creating build/scripts-2.7 > > copying and adjusting termsaver -> build/scripts-2.7 > > changing mode of build/scripts-2.7/termsaver from 644 to 755 > > running build_trans > > Compiling locale/ja.po > > Compiling locale/en.po > > running install_lib > > creating /usr/local/lib/python2.7/dist-packages/termsaverlib > > copying build/lib.linux-i686-2.7/termsaverlib/constants.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib > > creating /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/programmer.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/rssfeed.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/rfc.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/urlfetcher.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/jokes4all.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/dot.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > creating /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base > > copying build/lib.linux-i686-2.7/termsaverlib/screen/base/rssfeed.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base > > copying build/lib.linux-i686-2.7/termsaverlib/screen/base/urlfetcher.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base > > copying build/lib.linux-i686-2.7/termsaverlib/screen/base/filereader.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base > > copying build/lib.linux-i686-2.7/termsaverlib/screen/base/__init__.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base > > copying build/lib.linux-i686-2.7/termsaverlib/screen/__init__.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/asciiartfarts.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > creating /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/helper/position.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/helper/urlfetcher.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/helper/typing.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/helper/xmlreader.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/helper/__init__.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper > > copying build/lib.linux-i686-2.7/termsaverlib/screen/quotes4all.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/screen/randtxt.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen > > copying build/lib.linux-i686-2.7/termsaverlib/i18n.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib > > copying build/lib.linux-i686-2.7/termsaverlib/common.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib > > copying build/lib.linux-i686-2.7/termsaverlib/exception.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib > > copying build/lib.linux-i686-2.7/termsaverlib/__init__.py -> > > /usr/local/lib/python2.7/dist-packages/termsaverlib > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/constants.py to > > constants.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/programmer.py to > > programmer.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/rssfeed.py to > > rssfeed.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/rfc.py to rfc.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/urlfetcher.py to > > urlfetcher.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/jokes4all.py to > > jokes4all.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/dot.py to dot.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base/rssfeed.py > > to rssfeed.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base/urlfetcher.py > > to urlfetcher.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base/filereader.py > > to filereader.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/base/__init__.py > > to __init__.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/__init__.py to > > __init__.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/asciiartfarts.py > > to asciiartfarts.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper/position.py > > to position.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper/urlfetcher.py > > to urlfetcher.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper/typing.py > > to typing.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper/xmlreader.py > > to xmlreader.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/helper/__init__.py > > to __init__.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/quotes4all.py to > > quotes4all.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/screen/randtxt.py to > > randtxt.pyc > > byte-compiling /usr/local/lib/python2.7/dist-packages/termsaverlib/i18n.py > > to i18n.pyc > > byte-compiling /usr/local/lib/python2.7/dist-packages/termsaverlib/common.py > > to common.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/exception.py to > > exception.pyc > > byte-compiling > > /usr/local/lib/python2.7/dist-packages/termsaverlib/__init__.py to > > __init__.pyc > > running install_scripts > > copying build/scripts-2.7/termsaver -> /usr/local/bin > > changing mode of /usr/local/bin/termsaver to 755 > > running install_egg_info > > Writing /usr/local/lib/python2.7/dist-packages/termsaver-0.1_beta.egg-info > > writing list of installed files to '/tmp/termsaver.install.record.txt' > > Thank you for trying termsaver. > > bruno@development3;~$ > > > > > > Any help is much appreciated. I found very hard to do anything with > > distutils unless I open the source and see by myself what it can do or > > not... I was hoping there is a better way. > > > > Thank you in advance, > > Unfortunately, the install command won't actually run the install_data > command as a sub-command unless a non-empty list was passed to > data_files command in setup(). > > But I don't think your custom InstallData command is particularly > necessary. Try removing InstallData and instead do something like > this: > > data_files = [(os.path.join('share', 'locale', lang[:-3], 'LC_MESSAGES'), > [os.path.join('build', 'locale', lang[:-3], 'LC_MESSAGES', > 'termsaver.mo')]) > for lang in os.listdir('locale')] > > and > > setup( > ... > data_files=data_files, > ...) > > That should do what you're trying to do. > > Erik

1 0

Running `distribute` without installing it globally
by Tim Cuthbertson March 18, 2012

March 18, 2012

Hi all, I'm attempting to create a [zero install](http://0install.net) feed / package for distribute, for the purposes of being able to build software (using distribute) without having to first manually install distribute. Specifically nosetests, but I imagine it will be useful for lots of other software. This means I'll only really want the part of distribute that *builds* software - running 2to3, compiling C extensions if present, etc. If there's a specific subset of distribute I should be using that, it'd be good to know - but for now I'm building the the whole thing and just not invoking the other features. Anyway, the main requirements of a zero install feed are that the program must be relocatable, and must be runnable "as-is", without installing anything to well-known locations. This is similar to wanting to run a built version from within a checked-out workspace, in that the location of the built files is not some special system location. In attempting to do this (specifically for python 3), I've encountered some issues. The first is that `distutils.require("distribute")` doesn't work if distribute is not installed globally. This failed on program startup, because setuptools/package_index.py contains: user_agent = "Python-urllib/%s distribute/%s" % ( sys.version[:3], require('distribute')[0].version ) I've changed this to use setuptools.__version__, which is not the exact same thing but is probably close enough for a user-agent? Otherwise, perhaps the user-agent could be lazy-initted since you'd have little reason to use it if you're just building packages. The second issue is much more surprising: Once I got it running, any invocation would give me the error: $ python3 lib/easy_install.py --help usage: easy_install.py [options] requirement_or_url ... or: easy_install.py --help error: invalid command 'easy_install' I've taken the following line out of setuptools/command/easy_install.py: script_args = ['-q','easy_install', '-v']+argv, and replaced it with just: script_args = argv, I feel surely there was a good reason for this being here in the first place, so I'm curious about why it was broken for me. I've pushed my changes to bitbucket: https://bitbucket.org/gfxmonk/distribute. After these changes, it seems to at least run from an arbitrary directory without being installed globally. After all this, trying to build nosetests (using `python3 setup.py build`) still fails though, unfortunately - it seems to be using the system version of the setup() function, because I get the following warnings: /usr/lib/python3.2/distutils/dist.py:257: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.2/distutils/dist.py:257: UserWarning: Unknown distribution option: 'use_2to3' warnings.warn(msg) /usr/lib/python3.2/distutils/dist.py:257: UserWarning: Unknown distribution option: 'zip_safe' warnings.warn(msg) /usr/lib/python3.2/distutils/dist.py:257: UserWarning: Unknown distribution option: 'entry_points' warnings.warn(msg) ..and the built library gets syntax on errors when run under py3, presumably because py3 didn't actually run. Any idea how to get some more information on what path is being taken during the build process and why it's not invoking the distribute hotness? Cheers, - Tim.

1 1

get name of built egg
by Andrea Crotti March 17, 2012

March 17, 2012

Given the setuptools magic done by python setup.py bdist_egg is there a way to find out what will be the name of the final egg file? It would be really useful to know for me and I can't find any option to tell bdist_egg to let me know where it will write..

2 3

Re: [Distutils] RFC: Binary Distribution Format for distutils2/packaging
by Paul Moore March 16, 2012

March 16, 2012

On 14 March 2012 19:04, Tarek Ziadé <tarek(a)ziade.org> wrote: >> Please can we have a new format that only has a Python version in the >> filename if it matters? > > isn't that supposed to be the source release ? Yes, basically - at least as far as I understand. > Why would someone create a binary release when > it's pure Python ? I wish I knew. But people do - mostly egg format files. But I think this is partly because of the confusion between egg-as-distribution-format vs egg-as-directly-usable-object that PJE alludes to in his emails. If there's a binary egg available, how do I know whether it's needed without trying a source install and seeing if it works? And what about where it does, but doesn't install C accelerators because I have no compiler? The source works, but the binary is better. How would an automated installation process know? Binary installers for pure-Python projects exist, and cause confusion. (Example - IPython, see http://archive.ipython.org/release/0.12/) > or are you thinking about the auto-installable feature > for windows here ? No. I used to care about this, but no longer. I'm happy now to install anything that *can* be installed from source directly, using pip (or pysetup, once it works). > I think there are two different uses cases: > > - install a program or a lib manually -- where an auto-installer makes > sense. > - have a library installed by a tool, where an auto-installer is not really > needed. I'm not sure I'd characterise the cases like that, I tend to think of them as "wants to integrate with system standard policies" vs "wants to use Python specific approaches". But it's the same 2 cases. I used to be in the first camp, but I've switched and these days I'm firmly in the second. > I was thinking bdist_wininst and bdist_msi would stay around for people that > want to create self-installable archives, > and we would discuss a new format that is not self-installable. The key thing for me, as a user, is having packages that I cannot build myself available to me in a format that I can use. And secondarily to have an easy user experience. The following are possible installation scenarios: 1. pip/pysetup install PKG - transparent and simple, for source distributions that are pure-Python or I can build (no external dependencies and I have C installed) 2. pip/pysetup install PKG - new-format supplied by author (I assume the install command will auto-download the new format) 3. download egg/wininst file run converter to create new-format pip/pysetup install new-format-file tidy up the temporary files - egg or wininst supplied by author, assuming converters exist and are supplied with Python (add a "find the converter" step if they are 3rd party) 4. Install as system installer - MSI supplied by author, and I'm installing in system Python. 5. Cry - MSI supplied by author and I want to install in a virtualenv or similar. Basically, it's impossible (or at least, not worth the effort). To give me the best user experience, authors have to start supplying the new format. The hard part is getting authors to take up a new format (after all, they probably want to keep the old format as well, for users who haven't switched to pysetup, so you've just doubled their work). Alternatively, integrate the converters directly into pip/pysetup, so that eggs and wininsts are *transparently* converted on download, making case 3 look just like case 2. But at that point, what's the argument for authors distributing the new format, when the old ones work just as well for new-style users? The technical issues aren't hard, it's the social issues that need careful consideration. Paul.

5 8

easy_install problem
by Nitin Dhiman March 15, 2012

March 15, 2012

Greetings, My OS is Ubuntu Lucid lynx 10.04, with Python disutils python-setuptools version 0.6.10-4ubuntu1 I am behind proxy. http_proxy and https_proxy is defined as http://username:passwd@proxy-ip:port I am trying to use easy_install to install rosinstall using following command: nitin@nitin-desktop:~/Downloads$ sudo easy_install -U rosinstall vcstools [sudo] password for nitin: Searching for rosinstall Reading http://pypi.python.org/simple/rosinstall/ Download error: [Errno -2] Name or service not known -- Some packages may not be found! Reading http://pypi.python.org/simple/rosinstall/ Download error: [Errno -2] Name or service not known -- Some packages may not be found! Couldn't find index page for 'rosinstall' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ Download error: [Errno -2] Name or service not known -- Some packages may not be found! No local packages or download links found for rosinstall error: Could not find suitable distribution for Requirement.parse('rosinstall') This repeats couple of times. Is this issue related to proxy??? I do not face any problem when having a direct internet connnection. I had tried using pip also but i gets problems. Following is the output of log file. Downloading/unpacking rosinstall Getting page http://pypi.python.org/simple/rosinstall Could not fetch URL http://pypi.python.org/simple/rosinstall: <urlopen error [Errno -2] Name or service not known> Will skip URL http://pypi.python.org/simple/rosinstall when looking for download links for rosinstall Getting page http://pypi.python.org/simple/ Could not fetch URL http://pypi.python.org/simple/: <urlopen error [Errno -2] Name or service not known> Will skip URL http://pypi.python.org/simple/ when looking for download links for rosinstall Cannot fetch index base URL http://pypi.python.org/simple/ Cannot find requirement rosinstall, nor fetch index URL http://pypi.python.org/simple/ Exception information: Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/pip.py", line 252, in main self.run(options, args) File "/usr/lib/python2.6/dist-packages/pip.py", line 408, in run requirement_set.install_files(finder, force_root_egg_info=self.bundle) File "/usr/lib/python2.6/dist-packages/pip.py", line 1750, in install_files url = finder.find_requirement(req_to_install, upgrade=self.upgrade) File "/usr/lib/python2.6/dist-packages/pip.py", line 996, in find_requirement url_name = self._find_url_name(Link(self.index_urls[0]), url_name, req) File "/usr/lib/python2.6/dist-packages/pip.py", line 1073, in _find_url_name raise DistributionNotFound('Cannot find requirement %s, nor fetch index URL %s' % (req, index_url)) DistributionNotFound: Cannot find requirement rosinstall, nor fetch index URL http://pypi.python.org/simple/ The package I am trying to install is from ROS (www.ros.org) . The community of ROS has suggested to ask the solution in this community . I hope some one can solve the problem. Could this problem be because of any proxy rules???? I am not aware of these. regards prince

2 2