Mailman 3 July 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

GCC versions and binary egg names
by Chris Withers 06 Aug '10

06 Aug '10

Hi All, In addition to the UCS2/4 problems already described by MAL and which I've bumped into myself, I now have a problem with binary linux eggs where the GCC version doesn't match that of the system the egg is being installed on. Current egg metadata doesn't take either of these into account or even provide a way for the nature of the binary egg to be recorded. How're people coping with this? What are the future plans in this area? cheers, Chris

8 27

Announcing buildout_versions 1.0
by Chris Withers 03 Aug '10

03 Aug '10

Hi All, I'm pleased to announce the first release of buildout_versions. This is my take on buildout.dumppickedversions in that it's purpose is to make the user of a buildout aware if any package versions have been picked by buildout rather than specified by the buildout configuration. It has two important differences: - if no versions need to be picked, it generates no output - if you specify recording of picked versions to a file, that file is only ever appended to, not overwritten. The PyPI page is here: http://pypi.python.org/pypi/buildout_versions The documentation is here: http://packages.python.org/buildout_versions This extensions is also fully tested. If you have any problems or suggestions, please let me know on this list! cheers, Chris

2 3

buildout 2
by Jim Fulton 02 Aug '10

02 Aug '10

FYI. After 1.5 lands and the dust settles, I intend to look at refactoring buildout pretty significantly, primarily to make maintenance simpler. Jim -- Jim Fulton

3 2

Re: [Distutils] How to customize egg_info behavior
by P.J. Eby 01 Aug '10

01 Aug '10

At 12:39 PM 7/31/2010 -0700, Jason R. Coombs wrote: >I'm using setuptools 0.6c11. > >I'd like to programmatically customize the way the egg_info command >is run. That is, in my setup.py, I would like to run some functions >to determine the tag-build, tag-date, and tag-svn-revision >parameters to egg_info. Are there parameters > >How is this task best accomplished? Do I subclass the egg_info >Command? If so, do I just specify >cmdclass={'egg_info':my_custom_egg_info} ? Or would you recommend >another approach? You can just do this in your setup script: setup( ... options = dict(egg_info = dict(tag_build = "whatever", ...)), ... ) Replacing "whatever", of course, with your programmatic calculation.

2 1

How to customize egg_info behavior
by Jason R. Coombs 31 Jul '10

31 Jul '10

I'm using setuptools 0.6c11. I'd like to programmatically customize the way the egg_info command is run. That is, in my setup.py, I would like to run some functions to determine the tag-build, tag-date, and tag-svn-revision parameters to egg_info. Are there parameters How is this task best accomplished? Do I subclass the egg_info Command? If so, do I just specify cmdclass={'egg_info':my_custom_egg_info} ? Or would you recommend another approach? Regards, Jason

1 0

[buildout] extending a .cfg supplied by another package
by Chris Withers 30 Jul '10

30 Jul '10

Hi All, I'd like to be able to do: [buildout] extends=some.package:aconfig.cfg ...kinda like you can with templates in BFG, which I believe uses pkg_tools to do the hard work. What're the chances of that happening? cheers, Chris

5 11