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

docs/ vs doc/
by anatoly techtonik 23 Feb '11

23 Feb '11

Hi, I see that distutils2 promotes storing documentation in docs/ directory while Python sources use Doc/ I'd like to see this changed before distutils2 is released beta. In my projects checkouts there are 80 project that use doc/ directories. Among these are: - subversion - hg - sphinx - trac - scons - twisted docs/ directory is used by 61 project, the most famous are: - xalan - fop - moinmoin - cmd2 - googlecl There are some arguments for 'doc/': 1. there is no plural for 'documentation' 2. bin/ is a common name for storing executables, although there is plural for 'binary' 3. we still use src/ instead of sources/ Any thoughts/objections? -- anatoly t.

9 19

Re: [Distutils] easy_install with post-install script
by P.J. Eby 28 Sep '10

28 Sep '10

At 05:05 PM 9/27/2010 +0200, Lacko Roman wrote: >Thanks for reply, > > > Add a script to your package that performs the installation step > (or an option > > to an existing script), and then ask the user to run it after the > install is > > complete. >Yes this is how I resolved the problem before > > > (No, there's no automated way.) >Do You plan to support this in future ? I don't have a specific plan, but am open to finding ways to do it. Those ways, however, need to allow users to know what the post-install operations are doing/going to do (with explicit user consent), along with having uninstall capabilities. >Thanks >-Roman > > > -----Original Message----- > > From: P.J. Eby [mailto:pje@telecommunity.com] > > Sent: Monday, September 27, 2010 4:33 PM > > To: Lacko Roman; distutils-sig(a)python.org > > Subject: Re: [Distutils] easy_install with post-install script > > > > At 10:41 AM 9/27/2010 +0200, Lacko Roman wrote: > > >Hi, > > > > > >Is there some way to run some post-install script when installing the > > >python package with easy_install ? > > >I need to create some files in folder where the python interpreter is > > located. > > >BTW It is possible with bdist_wininst, because it support post > > >installation scripts, but not with easy_install. > > > > Add a script to your package that performs the installation step > (or an option > > to an existing script), and then ask the user to run it after the > install is > > complete. > > > > (No, there's no automated way.)

2 1

Re: [Distutils] easy_install with post-install script
by P.J. Eby 27 Sep '10

27 Sep '10

At 10:41 AM 9/27/2010 +0200, Lacko Roman wrote: >Hi, > >Is there some way to run some post-install script when installing >the python package with easy_install ? >I need to create some files in folder where the python interpreter is located. >BTW It is possible with bdist_wininst, because it support post >installation scripts, but not with easy_install. Add a script to your package that performs the installation step (or an option to an existing script), and then ask the user to run it after the install is complete. (No, there's no automated way.)

2 1

Re: [Distutils] Distribute error? datetimewidget.pot: File name too long
by P.J. Eby 27 Sep '10

27 Sep '10

Fascinating. It appears as though your virtualenv has both distribute 0.6.14 *and* setuptools 0.6c12dev on sys.path at the same time. However, I'm most curious about this one: At 10:52 PM 9/26/2010 +0100, Jon Hadley wrote: >paster_plugins fez.atcsv 0.3 () This looks like an error to me, and one that *could* create the behavior being seen. Your app should not be defining the paster_plugins entry point; instead, you are supposed to just have a setup_requires=['PasteScript'] in order to take care of it. What is probably happening now is that your package is claiming it implements this keyword argument, so any project that is built with your project on sys.path that uses this keyword (such as your own proejct) will try to add your project's runtime dependencies (i.e. setuptools and plone.app.z3cform) to sys.path. So, it tries to build those dependencies first. However, at that point, it appears fez.atcsv is *also* providing an entry point for the paster_plugins.txt egg-info writer... which is even worse, because it affects *every* app built, not just ones that use the paster_plugins setup() keyword. So, as soon as the dependency tries to build, it wants to have fez.atcsv built... so it tries to build fez.atcsv's dependencies... and so on, and so on, indefinitely. Here's how to fix the problem: First, remove all fez.atcsv-*.egg files or directories -- EVERYWHERE. Delete every last one off the system, no matter where it is. Second, remove the entry_points.txt file from the fez.atcsv.egg-info/ directory within your project source. Third and finally, remove the entire entry_points keyword from your setup() call in setup.py, and replace it with setup_requires=['PasteScript']. This would probably be sufficient to fix the problem if setuptools were first on your sys.path, since it has fixes for PasteScript's internal build recursion; I do not know if it will fix the problem with distribute, unless you first make sure PasteScript's dependencies are all installed. However, I'm pretty certain at this point that the bogus entry_points in your setup.py is the source of the entire problem, and explains why I could not reproduce it (as at no point would a copy of the broken fez.atcsv have been on my sys.path during any of my attempts, whereas it presumably was during most if not all of yours).

3 2

easy_install with post-install script
by Lacko Roman 27 Sep '10

27 Sep '10

Hi, Is there some way to run some post-install script when installing the python package with easy_install ? I need to create some files in folder where the python interpreter is located. BTW It is possible with bdist_wininst, because it support post installation scripts, but not with easy_install. Thank in advance Roman Lacko

1 0

Distribute error? datetimewidget.pot: File name too long
by Jon Hadley 25 Sep '10

25 Sep '10

I'm trying to install a custom package in a buildout managed Plone 3 site in /develop-src named (for the sake of argument) 'foobar.wontbloodywork'. Yet I keep getting an error 'z3cform.datetimewidget.pot: File name too long' I get the same result on a freshly built Ubuntu server with no previous eggs. The custom packages used to install fine in an older (12 month +) project. It was suggested to me (via the Plone Users mailing list) that this might be a distribute error. Can anyone on this list offer any insights? Results of buildout -vvvv below: Develop: '/Users/foobar/development/sites/gpi/gpi3/develop-src/foobar.wontbloodywork' in: '/Users/foobar/development/sites/gpi/gpi3/develop-src/foobar.wontbloodywork' /var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpXFTFnd -q develop -mxN -d /Users/foobar/development/sites/gpi/gpi3/develop-eggs/tmp00VAgBbuild install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . install_dir . Traceback (most recent call last): File "/var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpXFTFnd", line 11, in ? execfile('/Users/foobar/development/sites/gpi/gpi3/develop-src/foobar.wontbloodywork/setup.py') File "/Users/foobar/development/sites/gpi/gpi3/develop-src/foobar.wontbloodywork/setup.py", line 56, in ? paster_plugins = ["ZopeSkel"], File "/opt/local/lib/python2.4/distutils/core.py", line 110, in setup _setup_distribution = dist = klass(attrs) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/dist.py", line 225, in __init__ _Distribution.__init__(self,attrs) File "/opt/local/lib/python2.4/distutils/dist.py", line 240, in __init__ self.finalize_options() File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/dist.py", line 257, in finalize_options ep.require(installer=self.fetch_build_egg) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/pkg_resources.py", line 1966, in require working_set.resolve(self.dist.requires(self.extras),env,installer)) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/pkg_resources.py", line 544, in resolve dist = best[req.key] = env.best_match(req, self, installer) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/pkg_resources.py", line 786, in best_match return self.obtain(req, installer) # try and download/install File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/pkg_resources.py", line 798, in obtain return installer(requirement) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/dist.py", line 293, in fetch_build_egg return cmd.easy_install(req) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/command/easy_install.py", line 582, in easy_install return self.install_item(spec, dist.location, tmpdir, deps) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/command/easy_install.py", line 612, in install_item dists = self.install_eggs(spec, download, tmpdir) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/command/easy_install.py", line 802, in install_eggs return self.build_and_install(setup_script, setup_base) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/command/easy_install.py", line 1079, in build_and_install self.run_setup(setup_script, setup_base, args) File "/Users/foobar/.eggs/distribute-0.6.14-py2.4.egg/setuptools/command/easy_install.py", line 1070, in run_setup raise DistutilsError("Setup script exited with %s" % (v.args[0],)) distutils.errors.DistutilsError: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: Setup script exited with error: /var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/easy_install-1srx5w/plone.app.z3cform-0.5.0/temp/easy_install-9Uu00i/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-D3fuI0/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-ZmcdZR/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-hAO4T6/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-gabkaJ/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-eev8-a/collective.z3cform.datetimewidget-1.0.2/temp/easy_install--bZxqg/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-FeERFa/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-RT9zdd/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-WaJDIy/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-7Fa2cl/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-37Xaaj/collective.z3cform.datetimewidget-1.0.2/temp/easy_install-e_tXs0/collective.z3cform.datetimewidget-1.0.2/src/collective/z3cform/datetimewidget/locales/collective.z3cform.datetimewidget.pot: File name too long While: Installing. Processing develop directory '/Users/foobar/development/sites/gpi/gpi3/develop-src/foobar.wontbloodywork'. An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/private/var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpZ8LHi3/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 1660, in main File "/private/var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpZ8LHi3/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 394, in install File "/private/var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpZ8LHi3/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 634, in _develop File "/private/var/folders/N1/N1WTRWwWE5Gfqr-Sut+UVk+++TM/-Tmp-/tmpZ8LHi3/zc.buildout-1.4.3-py2.4.egg/zc/buildout/easy_install.py", line 894, in develop AssertionError

3 12

Distutils-SIG September 2010