Mailman 3 April 2010 - Distutils-SIG

Two fixes (at last)
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I have fixed two problems that a couple people noticed a while ago: * I folded in Amos Latteier's NT patches almost verbatim -- just changed an `os.path.sep == "/"' to `os.name == "posix"' and added some comments bitching about the inadequacy of the current library installation model (I think this is Python's fault, but for now Distutils is slavishly aping the situation in Python 1.5.x) * I fixed the problem whereby running "setup.py install" without doing anything else caused a crash (because 'build' hadn't yet been run). Now, the 'install' command automatically runs 'build' before doing anything; to make this bearable, I added a 'have_run' dictionary to the Distribution class to keep track of which commands have been run. So now not only are command classes singletons, but their 'run' method can only be invoked once -- both restrictions enforced by Distribution. The code is checked into CVS, or you can download a snapshot at http://www.python.org/sigs/distutils-sig/distutils-19990607.tar.gz Hope someone (Amos?) can try the new version under NT. Any takers for Mac OS? BTW, all parties involved in the Great "Where Do We Install Stuff?" Debate should take a good, hard look at the 'set_final_options()' method of the Install class in distutils/install.py; this is where all the policy decisions about where to install files are made. Currently it apes the Python 1.5 situation as closely as I could figure it out. Obviously, this is subject to change -- I just don't know to *what* it will change! Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Package versioning
by Timothy Docker 29 Apr '18

29 Apr '18

Hi all, I've been aware that the distutils sig has been simmerring away, but until recently it has not been directly relevant to what I do. I like the look of the proposed api, but have one question. Will this support an installed system that has multiple versions of the same package installed simultaneously? If not, then this would seem to be a significant limitation, especially when dependencies between packages are considered. Assuming it does, then how will this be achieved? I am presently managing this with a messy arrangement of symlinks. A package is installed with its version number in it's name, and a separate directory is created for an application with links from the unversioned package name to the versioned one. Then I just set the pythonpath to this directory. A sample of what the directory looks like is shown below. I'm sure there is a better solution that this, and I'm not sure that this would work under windows anyway (does windows have symlinks?). So, has this SIG considered such versioning issues yet? Cheers, Tim -------------------------------------------------------------- Tim Docker timd(a)macquarie.com.au Quantative Applications Division Macquarie Bank -------------------------------------------------------------- qad16:qad $ ls -l lib/python/ total 110 drwxr-xr-x 2 mts mts 512 Nov 11 11:23 1.1 -r--r----- 1 root mts 45172 Sep 1 1998 cdrmodule_0_7_1.so drwxr-xr-x 2 mts mts 512 Sep 1 1998 chart_1_1 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Fnorb_0_7_1 dr-xr-x--- 3 mts mts 512 Nov 11 11:21 Fnorb_0_8 drwxr-xr-x 3 mts mts 1536 Mar 3 12:45 mts_1_1 dr-xr-x--- 7 mts mts 512 Nov 11 11:22 OpenGL_1_5_1 dr-xr-x--- 2 mts mts 1024 Nov 11 11:23 PIL_0_3 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Pmw_0_7 dr-xr-x--- 2 mts mts 512 Nov 11 11:21 v3d_1_1 qad16:qad $ ls -l lib/python/1.1 total 30 lrwxrwxrwx 1 root other 29 Apr 10 10:43 _glumodule.so -> ../OpenGL_1_5_1/_glumodule.so lrwxrwxrwx 1 root other 30 Apr 10 10:43 _glutmodule.so -> ../OpenGL_1_5_1/_glutmodule.so lrwxrwxrwx 1 root other 22 Apr 10 10:43 _imaging.so -> ../PIL_0_3/_imaging.so lrwxrwxrwx 1 root other 36 Apr 10 10:43 _opengl_nummodule.so -> ../OpenGL_1_5_1/_opengl_nummodule.so lrwxrwxrwx 1 root other 27 Apr 10 10:43 _tkinter.so -> ../OpenGL_1_5_1/_tkinter.so lrwxrwxrwx 1 mts mts 21 Apr 10 10:43 cdrmodule.so -> ../cdrmodule_0_7_1.so lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 chart -> ../chart_1_1 lrwxrwxrwx 1 root other 12 Apr 10 10:43 Fnorb -> ../Fnorb_0_8 lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 mts -> ../mts_1_1 lrwxrwxrwx 1 root other 15 Apr 10 10:43 OpenGL -> ../OpenGL_1_5_1 lrwxrwxrwx 1 root other 33 Apr 10 10:43 opengltrmodule.so -> ../OpenGL_1_5_1/opengltrmodule.so lrwxrwxrwx 1 root other 33 Apr 10 10:43 openglutil_num.so -> ../OpenGL_1_5_1/openglutil_num.so lrwxrwxrwx 1 root other 10 Apr 10 10:43 PIL -> ../PIL_0_3 lrwxrwxrwx 1 mts mts 10 Apr 10 10:43 Pmw -> ../Pmw_0_7 lrwxrwxrwx 1 root other 10 Apr 10 10:43 v3d -> ../v3d_1_1

3 2

[Distutils-sig] distutils charter and interscript
by John Skaller 29 Apr '18

29 Apr '18

3 2

[buildout] branches languishing? (site-packages and distutils scripts)
by Chris Withers 02 Apr '12

02 Apr '12

Hi All, I'm wondering what the state of play is with the following branches: reinout-scripts gary-4-include-site-packages What more needs to happen for these to get merged to trunk and a release made? cheers, Chris

10 28

Beta release of zc.buildout 1.5.0
by Gary Poster 23 Jul '10

23 Jul '10

I have made a beta release of zc.buildout 1.5.0. Among other changes, this release includes the ability to use zc.buildout with a system Python, if you use the new z3c.recipe.scripts instead of zc.recipe.egg for generating scripts. Changelog: http://pypi.python.org/pypi/zc.buildout/1.5.0b1#b1-2010-04-29 In my experience, working with a system ("non-clean") Python can be fragile in many ways. However, this release addresses the problems I have encountered so far. Your feedback is welcome. I hope to make a final release sometime next week. Gary

10 28

Bootstrap script for package management tool in Python 2.7 (Was: Re: [Python-Dev] At least one package management tool for 2.7)
by anatoly techtonik 07 Jul '10

07 Jul '10

So, there won't be any package management tool shipped with Python 2.7 and users will have to download and install `setuptools` manually as before: "search" -> "download" -> "unzip" -> "cmd" -> "cd" -> "python setup.py install" Therefore I still propose shipping bootstrap package that instruct user how to download and install an actual package management tool when users tries to use it. So far I know only one stable tool - `easy_install` - a part of `setuptools` package. The required behavior for very basic user friendliness: 1. user installs Python 2.7 2. user issues `python -m easy_install something` 3. user gets message 'easy_install' tool is not installed on this system. To make it available, download and install `setuptools` package from http://pypi.python.org/pypi/setuptools/ 4. the screen is paused before exit (for windows systems) Other design notes: 1. if package tries to import `easy_install` module used for bootstrap, it gets the same ImportException as if there were no `easy_install` at all 2. bootstrap module is overwritten by actual package when users installs it So, do we need a PEP for that? How else can I know if consensus is reached? Anybody is willing to elaborate on implementation? P.S. Please be careful to reply to relevant lists -- anatoly t. On Mon, Mar 29, 2010 at 9:37 AM, Tarek Ziadé <ziade.tarek(a)gmail.com> wrote: > 2010/3/29 anatoly techtonik <techtonik(a)gmail.com>: > [..] >> It is really hard to follow. You should at least change subjects when >> switching topic. > > I was talking about the work going on and the decisions taken lately. > > I never change topics of threads mails when there's less than 100 mails, > because I find it way more confusing :) > >> >> So, what is the verdict? Will there be a package management tool or >> bootstrap package for it shipped with Python 2.7 or not? > > As I said in the mail you've quoted, all improvements are made in > Distutils2. So the answer is no. > Python 2.7b1 is due in less than a week anyways, so any new > development on this topic will happen after. > > Basically Python 2.7 == Python 2.6 in term of packaging. > > Regards > Tarek > > -- > Tarek Ziadé | http://ziade.org >

11 29

new zc.buildout and virtualenv no longer friends?
by Chris McDonough 30 Apr '10

30 Apr '10

I have a relatively simple buildout that is a directory which is also a virtualenv (the buildout directory was prepped after checkout with Python 2.4 "virtualenv --no-site-packages ." and the bootstrap was run using the resulting "bin/python"). Just now, I had to rerun bin/buildout in that existing directory, and I got this: [chrism@thinko deformsite]$ bin/buildout Getting distribution for 'zc.buildout'. Got zc.buildout 1.5.0b1. Upgraded: zc.buildout version 1.5.0b1; restarting. Generated script '/home/chrism/projects/deformsite/bin/buildout'. Develop: '/home/chrism/projects/deformsite/src/deformsite' Develop: '/home/chrism/projects/deformsite/src/deform' Develop: '/home/chrism/projects/deformsite/src/colander' Getting distribution for 'zc.recipe.egg'. Traceback (most recent call last): File "<string>", line 1, in ? File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/__init__.py", line 2, in ? from setuptools.extension import Extension, Library File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/extension.py", line 1, in ? from distutils.core import Extension as _Extension File "/home/chrism/projects/deformsite/lib/python2.4/distutils/__init__.py", line 3, in ? import warnings ImportError: No module named warnings An error occured when trying to install zc.recipe.egg 1.2.3b1. Look above this message for any errors that were output by easy_install. While: Installing. Getting section deformsite. Initializing section deformsite. Installing recipe zc.recipe.egg. Getting distribution for 'zc.recipe.egg'. Error: Couldn't install: zc.recipe.egg 1.2.3b1 I had built a new virtualenv'ed buildout only a few hours before it the new zc.buildout was released with the most recent releases of everything. I had seen a new release of zc.buildout went up, so I figured I just needed to kinda start from scratch. So subsequently I blew everything away and did what I usually do when I want to start over: chrism@thinko projects]$ svn co $REPOZE_SVN/buildouts/deformsite <snip> Checked out revision 9276. [chrism@thinko projects]$ cd deformsite [chrism@thinko deformsite]$ virtualenv --no-site-packages . New python executable in ./bin/python Installing setuptools.............done. [chrism@thinko deformsite]$ bin/python bootstrap.py Creating directory '/home/chrism/projects/deformsite/parts'. Creating directory '/home/chrism/projects/deformsite/eggs'. Creating directory '/home/chrism/projects/deformsite/develop-eggs'. Getting distribution for 'setuptools'. Got setuptools 0.6c11. But when I went to run it, I got this: Generated script '/home/chrism/projects/deformsite/bin/buildout'. [chrism@thinko deformsite]$ bin/buildout Traceback (most recent call last): File "bin/buildout", line 14, in ? import site # imports custom buildout-generated site.py File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 661, in ? main() File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 628, in main virtual_install_main_packages() File "/home/chrism/projects/deformsite/parts/buildout/site.py", line 546, in virtual_install_main_packages f = open(os.path.join(os.path.dirname(__file__), 'orig-prefix.txt')) IOError: [Errno 2] No such file or directory: '/home/chrism/projects/deformsite/parts/buildout/orig-prefix.txt' If you were paying attention, you'd notice that I made the buildout dir into a virtualenv above, which I've been doing for a long time now to get actual isolation. So at that point, I tried to pin zc.buildout and zc.recipe.egg to an older version by adding the following to my buildout.cfg: versions = versions [versions] zc.buildout = 1.4.3 zc.recipe.egg = 1.2.2 But when I then did the same dance that blew up above with the version pins, it now blew up differently: [chrism@thinko projects]$ cd deformsite [chrism@thinko deformsite]$ virtualenv --no-site-packages . New python executable in ./bin/python Installing setuptools.............done. [chrism@thinko deformsite]$ bin/python bootstrap.py Creating directory '/home/chrism/projects/deformsite/parts'. Creating directory '/home/chrism/projects/deformsite/eggs'. Creating directory '/home/chrism/projects/deformsite/develop-eggs'. Getting distribution for 'setuptools'. Got setuptools 0.6c11. Getting distribution for 'zc.buildout==1.4.3'. Traceback (most recent call last): File "<string>", line 1, in ? File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/__init__.py", line 2, in ? from setuptools.extension import Extension, Library File "/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/extension.py", line 1, in ? from distutils.core import Extension as _Extension File "/home/chrism/projects/deformsite/lib/python2.4/distutils/__init__.py", line 3, in ? import warnings ImportError: No module named warnings An error occured when trying to install zc.buildout 1.4.3. Look above this message for any errors that were output by easy_install. While: Bootstrapping. Getting distribution for 'zc.buildout==1.4.3'. Error: Couldn't install: zc.buildout 1.4.3 I pdb stepped through this, and it dies when it reexecutes Python via os.spawnle of sys.executable (not on the initial execution of "python bootstrap.py"): [chrism@thinko deformsite]$ bin/python bootstrap.py > /home/chrism/projects/deformsite/bootstrap.py(44)?() -> assert os.spawnle( (Pdb) l 39 40 ws = pkg_resources.working_set 41 42 import pdb; pdb.set_trace() 43 44 -> assert os.spawnle( 45 os.P_WAIT, sys.executable, sys.executable, 46 '-c', cmd, '-mqNxd', tmpeggs, 'zc.buildout', 47 dict(os.environ, 48 PYTHONPATH= 49 (Pdb) p sys.executable, cmd, tmpeggs ('/home/chrism/projects/deformsite/bin/python', 'from setuptools.command.easy_install import main; main()', '/tmp/tmpEduLSX') (Pdb) p ws.find(pkg_resources.Requirement.parse('setuptools')).location '/home/chrism/projects/deformsite/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg' (Pdb) But sure enough, when I run it with a "real" Python instead of the virtualenv it works. Likely, the recent developers buildout of don't use virtualenv, so they won't have seen this behavior. I don't have the fortitude to debug buildout right now, and the isolation of a virtualenv keeps us sane. Ideally, I could change the buildout.cfg somehow to ignore the new buildout release entirely to get back to a state where buildout could be driven with a virtualenv-Python. Any hints? - C

6 11

building with static dependencies
by Chris Withers 30 Apr '10

30 Apr '10

Hi All, I'd like to build some packages into eggs such that I can easilly install them with virtual_env or buildout. The packages in question are numpy and scipy, at the moment. Are there parameters I can pass to "python setup.py build" or "python setup.py bdist_egg" that will cause the egg to be built will all its dependencies statically linked and included within the egg? (ie: so I can build once on linux and once on windows, put the binary eggs in our local index and then not have to worry about the build proceses and convoluted dependencies on other machines of a similar architecture) cheers, Chris

2 4

Re: [Distutils] [issue107] bdist_egg --bdist-dir param not working quite as expected
by P.J. Eby 30 Apr '10

30 Apr '10

At 01:18 AM 4/30/2010 +0000, Patrick Ting wrote: >So when specifying a build directory through the --bdist-dir param >to anything than the default directory: >1. (as expected) a build directory is created, the pyc files are >generated in this directory, and then the directory is deleted. >2. (bug) build/ directory in the cwd is always created with the >original .py files copied into it. Just for the benefit of anybody tracking this on the mailing list, the issue is that setting the build directory in this way only changes bdist_egg's build directory, not any other command's build directory (such as build_py). This is an artifact of distutils design, where you set options to commands like "build" and "install", which are then inherited by subcommands. The "distutils correct" way to do what the OP is trying to do is therefore: setup.py build --build-base=/whatever bdist_whatever As this will pass the build base onto all the subcommands. This is the same pattern for bdist_egg, bdist_wininst, bdist_dumb, etc. Maybe distutils2 should have a cleaner way of doing this sort of thing, if it's not being built on the same infrastructure.

1 0

buildout: bootstrap.py in 1.5.0b1 + python 2.5
by Rodrigo Moraes 30 Apr '10

30 Apr '10

Hey, I'm facing a problem running the bootstrap.py from buildout 1.5.0b1. The errors are pasted here: http://paste.pocoo.org/show/208025/ This error occurs only when I use Python 2.5; with 2.6 it works fine. Also it happens even if i set the flag --distribute. So for the time being I'm using the bootstrap from 1.4.3 on python 2.5, as it works well. I tried to debug it but I'm not familiar with the libraries and had no success. Could anybody please confirm that it is not working with Python 2.5 so that I know that the problem is not in my environment? :) thank you, rodrigo

2 3