Mailman 3 October 2011 - Distutils-SIG

Two fixes (at last)
by Greg Ward April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

3 2

[buildout] branches languishing? (site-packages and distutils scripts)
by Chris Withers April 2, 2012

April 2, 2012

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

Additional trove classifiers for Plone
by Alex Clark Nov. 15, 2011

Nov. 15, 2011

Hi, The Plone project[1] has the need for additional trove classifiers to track add-on compatibility by version. Is something that could be added to: - http://pypi.python.org/pypi?%3Aaction=list_classifiers ? Or should we implement these internally?[2] Are there any repercussions in doing so? Thanks for any feedback. Alex [1] http://plone.org [2] https://github.com/collective/Products.PloneSoftwareCenter -- Alex Clark · http://aclark.net

3 6

Odd limitation in packaging/distutils2
by Paul Moore Nov. 4, 2011

Nov. 4, 2011

This seems odd... PS D:\Data\PyPI> D:\Data\cpython\PCbuild\python -m packaging.run install nose installing third-party projects from an uninstalled Python is not supported And yet after downloading the nose source... PS D:\Data\PyPI> bsdtar xzf D:\Downloads\Python\nose-1.1.2.tar.gz PS D:\Data\PyPI> cd .\nose-1.1.2 PS D:\Data\PyPI\nose-1.1.2> D:\Data\cpython\PCbuild\python -m packaging.run install Installing from source directory: 'D:\\Data\\PyPI\\nose-1.1.2' Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.14.tar.gz Extracting in c:\users\gustav\appdata\local\temp\tmpecso_w Now working in c:\users\gustav\appdata\local\temp\tmpecso_w\distribute-0.6.14 Building a Distribute egg in D:\Data\PyPI\nose-1.1.2 warning: no files found matching 'Makefile' under directory 'docs' warning: no files found matching 'indexsidebar.html' under directory 'docs' creating build creating build\src ... etc (The build actually failed, but for reasons unrelated to the fact that it's an uninstalled Python, as far as I can see). Why not allow installing direct from PyPI? Paul.

4 10

Some distutils2/packaging questions
by Paul Moore Nov. 3, 2011

Nov. 3, 2011

Hi, I hope this is the right list for usage questions on distutils2/packaging. If not, please point me at the correct list. I'm looking at how I'd translate existing setup.py configurations into the new setup.cfg format. One situation I'm not sure how to deal with is the package_data argument to setup(). This allows me to specify data files which are to be installed as part of a package. How would I do this in distutils2/packaging? The resources entry seems like the intended place, but I don't see how I can specify the destination without making too many assumptions about precisely where the package will get installed. Any suggestions? Thanks, Paul.

2 1

virtualenv & pypi-server
by Andrea Crotti Oct. 31, 2011

Oct. 31, 2011

After reading everything was possible to read on setuptools and friends, I'm a bit confused... I have the following situation: suppose that there is a framework composed by many many eggs, which doesn't change very often. Then there are N applications using this framework, where every application is also composed by 2-3 eggs, and everything is run in a "funny" way (using Envisage). So at the moment every application fiddles around with the global easy_install.pth, which is bad and needs to be changed, and I have to figure out how. My idea would be to - have a global pypi-server running on localhost - every application is in a virtualenv (or buildout environment) and uses this local pypi-server I'm doing a few experiments, but already I'm not able to make my virtual env to fetch from my local pypi-server, what is the magic setting for that? The other future problems that I still see now are: 1. I have to be able to develop also the eggs from the framework 2. I have to make everything very simple to do from and Eclipse 3. These applications have to be shared on SVN, so maybe zc.buildout might be a better choice in this sense. Thanks a lot, Andrea

2 14

question re: easy_install and macports
by Chris Jerdonek Oct. 28, 2011

Oct. 28, 2011

Hi, I have a quick question regarding easy_install and MacPorts. I tried easy_installing nose while using MacPorts (Python 2.6.7 / py26-distribute @0.6.24_0 / MacPorts version 2.0.3) -- > sudo python -m easy_install nose This worked, except it installed the nosetests script into-- /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin but did not create an alias in-- /opt/local/bin So nosetests is not automatically in the path. Was this a problem with MacPorts, easy_install, or nose? Whose responsibility was it to create the alias? Thanks a lot, --Chris

3 5

Status of distutils & Co.?
by Hartmut Goebel Oct. 28, 2011

Oct. 28, 2011

Hi, while lurking on this lists for quite some month, I'm still wondering about the status of all the different distutils tools, including setuptool, pkg_resources, pip, ...). To my impression, there are some efforts around, but I'm missing some kind of overview or strategy. Beside the forest of tools, it seams to me, as if the distribution format is not "stable": pip seams to prefer archives over eggs. Is there some PEP describing the status and future of Python packaging? -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de Monatliche Kolumne: http://www.cissp-gefluester.de/ Goebel Consult ist Mitglied bei http://www.7-it.de

2 1