Distutils-SIG June 2008

distutils-sig@python.org

38 participants
50 discussions

Re: [Distutils] [venv] Re: Changes & News / 1.1 / * Added support for Python 2.6.

by Ian Bicking

d2m wrote: > You could go on and add another 3 modules > ('linecache','_abcoll','abc') to REQUIRED_MODULES just to find that > setuptools itself cannot be copied to my_env/lib/python2.6/site- > packages -- because there is no such distribution (2.6) right now: > > Downloading http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c8-py2.6.egg… > run python2.6 ez_setup.py, gets you almost the same error.) > > How did you install setuptools and virtualenv to make it functional? *I* haven't, because I don't have Python 2.6 and haven't tried it with that. I've added the other modules, but I'm not sure how to deal with the issue of a lack of a 2.6 setuptools egg. So, copying the distutils list: what's the best way to handle setuptools installation on Python 2.6? -- Ian Bicking : ianb(a)colorstudy.com : http://blog.ianbicking.org

12 years, 8 months

[issue24] Rename easy_install

by Armin Ronacher

New submission from Armin Ronacher <armin.ronacher(a)active-4.com>: Currently the egg installation script is called "easy_install". I would propose to rename it to something like "pyegg" or something similar. Mainly because "easy_install" is a very generic name and doesn't include anything related with python in the name which causes confusion. Additionally if easy_install gets an uninstallation feature the name is wrong too. ---------- messages: 47 nosy: aronacher priority: wish status: unread title: Rename easy_install _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue24> _______________________________________________

12 years, 8 months

What is needed by an uninstall command to be useful ?

by David Cournapeau

Hi, An uninstall command is a long-time wanted feature of distutils. I was wondering why it was not implemented: what does it need to do to be useful ? AFAIK, make uninstall in autotools simply removes currently installed files, with currently refering to the current configured value of prefix and all. Isn't this enough (I am interested in a 'pure' distutils command, not a setuptools one) ? What would be the minimum semantics needed for an uninstall command ? cheers, David

12 years, 8 months

Re: [Distutils] Creating rpm's for multiple python versions?

by Phil Schwartz

From: phil_schwartz(a)users.sourceforge.net Thanks for the reference Ignacio, however, I'm not sure how this applies to packaging the rpm in my current build environment. [Quote] If you are installing anything into the global site_packages directory, use the following trick. First, define python_sitelib at the top of your specfile: %{!?python_sitelib: %define python_sitelib %(%{__python} -c \ "from distutils.sysconfig import get_python_lib; print get_python_lib()")} [End Quote] since I don't have a spec file (distutils may create one as necessary and delete it). Running the following command returns the expected result: $ python2.3 -c "from distutils.sysconfig import get_python_lib; print get_python_lib()" /usr/lib/python2.3/site-packages But not sure how to include this in distutils (setup.py, setup.cfg, MANIFEST.in, etc). Certainly, someone else be packaging their python apps for multiple python versions. Thanks for any addition leads, Phil Ignacio Vazquez-Abrams wrote: You may want to consider reading Fedora's Python packaging guidelines[1]. [1] http://fedoraproject.org/wiki/Packaging/Python On Fri, 2008-06-13 at 14:36 -0700, Phil Schwartz wrote: > > I have a Fedora Core 7 development server that has python2.3, > > python2.4 and python2.5 installed. I'd like to build rpm's of my > > application for each > > of these versions of python. > > How can I force the rpm's to include the proper site-packages path > > (for python2.3 that would be "/usr/lib/python2.3/site-packages/")? -- Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com>

12 years, 8 months

There should be a no-index on simple pypi index

by Ian Bicking

I just did a search for "pyaudio" and this link: http://pypi.python.org/simple/PyAudio/ showed up above this link: http://pypi.python.org/pypi/PyAudio/0.2.0 If <meta name="robots" content="noindex"> was added to the simple pages that would help. -- Ian Bicking : ianb(a)colorstudy.com : http://blog.ianbicking.org

12 years, 8 months

[buildout] import develop eggs

by stefan tjarks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not sure where to post this, so if it's the wrong list please point me to the right one. I started using zc.buildout with django and are using djangorecipe[1]. After running buildout and trying to start django it fails trying to import my development module. Here is what I did in more detail. My folder structure: root/ bootstrap.py buildout.cfg src/ myapp/ setup.py src/ ... The buildout.cfg: [buildout] parts = django eggs = psycopg2 develop = src/myapp [django] recipe = djangorecipe version = trunk django_location = ${buildout:directory}/django_src settings = development eggs = ${buildout:eggs} project = instance Running bootstrap.py and bin/buildout works fine and gives me a develop-eggs directory with an .egg-link file as well as a bin/django file. After inserting 'myapp' into djangos settings file I tried to start django with 'bin/django runserver' and it failed with ImportError: No module named myapp The bin/django file is basically a wrapper, that sets the python path to all eggs and the project root directory. #!/home/dev/python2.5/bin/python import sys sys.path[0:0] = [ '/home/dev/eggs/psycopg2-2.0.7-py2.5-linux-ppc.egg', '/home/dev/eggs/djangorecipe-0.8-py2.5.egg', '/home/dev/eggs/zc.recipe.egg-1.0.0-py2.5.egg', '/home/dev/eggs/zc.buildout-1.0.6-py2.5.egg', '/home/dev/eggs/setuptools-0.6c8-py2.5.egg', '/home/dev/parts/django', '/home/dev', ] import djangorecipe.manage if __name__ == '__main__': djangorecipe.manage.main('instance.development') I don't see what I have missed. I do see that the develop-eggs directory is nowhere mentioned in the generated files, but thought that setuptools would take care of that and made the dev eggs importable. Regards - -stj [1] https://launchpad.net/djangorecipe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIVfMvwRdcaudH4ncRAvULAJsEzXnSpcX2MkelhQ/o+WRAGAAd/gCgmJ7e /r3qUz9V5VbYIhkK4jJM4K4= =wtjq -----END PGP SIGNATURE-----

12 years, 8 months

Creating rpm's for multiple python versions?

by Phil Schwartz

I have a Fedora Core 7 development server that has python2.3, python2.4 and python2.5 installed. I'd like to build rpm's of my application for each of these versions of python. Python2.5 (/usr/bin/python, /usr/bin/python2, /usr/bin/python2.5) is the default version but the others are available from /usr/bin/python2.3 and /usr/local/bin/python2.4 (both /usr/bin and /usr/local/bin are in my $PATH). I've tried the following: python2.3 setup.py bdist_rpm --python python2.3 \ --release python2.3 --binary-only python2.4 setup.py bdist_rpm --python python2.4 \ --release python2.4 --binary-only python2.5 setup.py bdist_rpm --python python2.5 \ --release python2.5 --binary-only All of the commands complete successfully, however, upon examining the generated dist/ rpm's for 2.3 and 2.4 I've noticed that the "site-packages" files are all relative the python2.5. That is, for the 2.3 rpm, there are files that contain the path "/usr/lib/python2.5/site-packages/...". How can I force the rpm's to include the proper site-packages path (for python2.3 that would be "/usr/lib/python2.3/site-packages/")? Thanks for any info, Phil

12 years, 8 months

[issue25] Prefer release versions of projects

by Chris Galvan

New submission from Chris Galvan <cgalvan(a)mail.utexas.edu>: Currently there is no ability to declare a preference for a release of a project. For example, I'd like to say my project requires "a release of foo >= 2.0, <3.0". I'd then like easy_install/setuptools to only pick releases (no qualifiers of any kind alpha, beta, dev, etc.) of 2.0, 2.1, 2.2, 2.3, 2.4, .... As a further example, it should totally ignore '2.5a1' and '2.6_r15669' and instead would fetch '2.2' if it existed in the same repository. It would be nice if this was the default behavior unless the user specified an additional flag to accept qualifiers(which would return the behavior to its previous state). Also, it would fall back on eggs with qualifiers if no releases were found. ---------- messages: 48 nosy: cgalvan priority: feature status: chatting title: Prefer release versions of projects _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue25> _______________________________________________

12 years, 8 months

py2exe finding dll's

by Eli Bendersky

Hello, I've always assumed that py2exe uses modulefinder (or rather a self-written version thereof) to find the modules used by the packaged application. However, I see that py2exe manages to find things that modulefinder doesn't find, such as DLLs. For example, when packaging an app that uses wxPython, modulefinder finds only the relevant .py and .pyd / .pyo files, while py2exe also finds all the wx DLLs. What kind of additional searches does py2exe do to find all the required infromation? Eli

12 years, 8 months

uninstall feature

by chris

A few days ago I submitted a ticket for adding an uninstall feature in setuptools. Today I submitted a patch that implements it. If anyone would like to try it out and give feedback, the ticket (and patch) is here: http://bugs.python.org/setuptools/issue21 Thanks, Chris

12 years, 8 months

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 June 2008