Mailman 3 December 2006 - Distutils-SIG

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

eggs and Python Unicode variants (UCS2, UCS4)
by Martijn Faassen 29 May '09

29 May '09

Hi there, In the lxml project (http://codespeak.net/lxml), we've just noticed the following problem with lxml eggs: you can easy_install an egg that won't work for your Python. This is because Python can be compiled with either 2 or 4 bytes unicode as its internal representation. Any egg that contains compiled C code that uses unicode such as lxml will run into trouble: if it's compiled with a 4 bytes unicode Python, it won't work on a 2 bytes unicode Python, and vice versa. This problem is fairly common in Linux. Many distributions such as Ubuntu and Fedora compile their python with 4 bytes unicode internal representation. If you compile a Python interpreter by hand it defaults to 2 bytes unicode, however. Hand-building a Python interpreter is done fairly commonly by Linux sysadmins for various reasons. It would therefore be very nice if it became possible to make eggs for the different unicode compilation options of Python. This configuration dimension is a real world issue for any binary Python module that does anything with unicode text.. In an earlier mail to this list: http://mail.python.org/pipermail/distutils-sig/2005-October/005222.html M.-A. Lemburg and Phillip Eby had the following discussion: [MAL] >>Please make sure that your eggs catch all possible >>Python binary build dimensions: >> >>* Python version >>* Python Unicode variant (UCS2, UCS4) >>* OS name >>* OS version >>* Platform architecture (e.g. 32-bit vs. 64-bit) [PJE] >As far as I know, all of this except the Unicode variant is captured in >distutils' get_platform(). And if it's not, it should be, since it >affects any other kind of bdist mechanism. I'm not sure whether this means this needs to be escalated from setuptools to the Python interpreter level itself. With this mail, I've done the job escalating this lxml problem to what appears to be the right place, though. :) Thanks, Martijn

5 5

Re: [Distutils] setuptools extras_require
by Matt Good 26 Apr '07

26 Apr '07

On Thu, 2006-12-14 at 07:15 +0100, Elvelind Grandin wrote: > Perhaps I wasn't totally clear. what I meant was something like this. > > extras_require = { > "default" : ["SQLObject==bugfix,>=0.7.1dev-r1860,<=0.7.99"], > "future" : ["Genshi>=0.3", "SQLAlchemy>=0.3"] > }, That may be ok for the example, but what happens if you add another extra "foo" for some optional feature. Installing "TurboGears[foo]" won't select either the "default" or "future" extras, so you don't really get all the requirements. >From a semantic perspective I think listing these as "extras" is odd. One of either SQLObject or SQLAlchemy is required for installation, so it's not just an "extra" feature. I think extras have been used for this as a workaround to setuptools not supporting ORed requirements, but I'd like to see that fixed. I tend to think in terms of Debian packages where stuff like SA or SO would be listed as "depends" meaning that they're strictly required, so in setuptools this would correspond to "install_requires". On the other hand I believe Paste is still an optional package used in TurboGears for stuff like the interactive traceback display, so it'd be a Debian "recommends", or setuptools "extras". Using "|" as a separator for ORing TurboGear's requirements might look something like this (ignoring version numbers for simplicity): install_requires = [ "SQLObject | SQLAlchemy", "Kid | Genshi", ], extras_require = { "fancy_tb": ["Paste"], } Setuptools would check if either SQLObject or SQLAlchemy was already installed, if not it'd try from left to right until it successfully installed one of the requirements. I suppose extras could still be used as aliases for something like the "future" requirements to make it easier for users to install this set of packages: extras_require = { "standard": ["Kid", "SQLObject"], "future": ["Genshi", "SQLAlchemy"], "fancy_tb": ["Paste"], } Alternatively tuples could be substituted to define ORed requirements like: install_requires = [ ("SQLObject", "SQLAlchemy"), ("Kid", "Genshi"), ] Comments? -- Matt Good > On 12/12/06, Matt Good <matt(a)matt-good.net> wrote: > > On Tue, 2006-12-12 at 16:32 +0100, Elvelind Grandin wrote: > > > Or use a magic extra name like "default" which is used if no other > > > extra is selected. > > > > This doesn't really address the full issue, since there may be several > > sets of alternative dependencies for different requirements. > > > > Following the TurboGears example it needs an ORM from "SQLObject or > > SQLAlchemy" and a template engine from "Kid or Genshi". So it'd need > > defaults for each, not just a single default. > > > > > On 12/11/06, Elvelind Grandin <elvelind(a)gmail.com> wrote: > > > > Not really > > > > > > > > extras_require = { > > > > 'PDF': ["ReportLab>=1.2", "RXP"], > > > > } > > > > extras_exclude = { > > > > 'PDF': ["Foo"], > > > > } > > > > > > > > might work. even if it's not that pretty. > > > > > > > > On 12/10/06, Phillip J. Eby <pje(a)telecommunity.com> wrote: > > > > > At 08:28 PM 12/10/2006 +0100, Elvelind Grandin wrote: > > > > > >Is there any way to exclude packages in extras_require as opposed to > > > > > >just include them. In Turbogears we have Sqlobject in by default. but > > > > > >if the extra "future" is used it should drop SO and install sqlalchemy > > > > > >instead. > > > > > > > > > > Not currently, no. Do you have any suggestions as to how this might be > > > > > spelled in the requirements API? > > > > > > > > > > > > > > > > > > > > > > -- > > > > cheers > > > > elvelind grandin > > > > > > > > > > > > > > > >

5 6

HTTP authentication support
by David Smith 05 Apr '07

05 Apr '07

Hello, I needed support in easy_install for installing from HTTP digest and basic authenticated sites so I wrote the included patch. It currently supports specifying username and password information at the command line (however misguided that may be) and prompting the user interactively. It should also be easy to integrate with graphical interfaces. Please consider it for inclusion in the next release. Thanks, -- David D. Smith

6 13

Building an egg from Subversion using zc.buildout
by Nathan R. Yergler 12 Feb '07

12 Feb '07

I'm using zc.buildout for deploying a handful of applications, and one of our dependencies doesn't have eggs or "correctly" formatted pages (that would allow easy_install to track down the repository for direct building from source). Does zc.buildout provide any way to build an egg from a Subversion URL? Something with similar behavior to: easy_install -m -d ./eggs http://path/to/svn/repos I'm happy to write a recipe if necessary, just thought I'd make sure someone else hadn't already scratched this itch. Thanks, Nathan

5 40

HTTP authentication support
by David Smith 29 Dec '06

29 Dec '06

Hello, I needed support in easy_install for installing from HTTP digest and basic authenticated sites so I wrote the included patch. It currently supports specifying username and password information at the command line (however misguided that may be) and prompting the user interactively. It should also be easy to integrate with graphical interfaces. Please consider it for inclusion in the next release. Thanks, -- David D. Smith

2 1

configuration files preservation
by Roman Kurakin 28 Dec '06

28 Dec '06

While working on one project I've met a problem that I can't to specify to not touch my configuration files for python package that uses setup.py technique. To solve this problem I've implemented the following solution that works for me. If this idea worths it, I can make a patch relative needed version of python. Here is the patch I've done for that project (inlined here to show the idea). # HG changeset patch # Node ID 286864b5c6a30d0ebba5fc99876013c85c06ab59 # Parent fc4dfd9ad64f477a0326995bea7cda12e33ddb39 Add 'preserve files' functionality to setup() while installation. (clean version) diff -r fc4dfd9ad64f -r 286864b5c6a3 setup.py --- a/setup.py Wed Dec 13 12:50:46 2006 +0300 +++ b/setup.py Mon Dec 18 14:01:34 2006 +0300 @@ -26,17 +26,66 @@ # POSSIBILITY OF SUCH DAMAGE. from distutils.core import setup +from distutils.command.install_data import install_data +from distutils.util import change_root, convert_path +from types import StringType -import sys +import sys,os pyver = "%d.%d" % sys.version_info[0:2] + +class smart_install_data(install_data): + def run(self): + # Use revers order for safe removal + for i in range(len(self.data_files)-1, -1, -1): + f = self.data_files[i] + if type(f) is StringType: + continue + if len(f) <= 2: + continue + # Ok, we have additional value, do some magick according it. + if f[2] != "preserve": + # Nope, we do not know it. Just ignore for now. + # Should we scream about it? + continue + # Check a tuple with path to install to and a list of files + dir = convert_path(f[0]) + if not os.path.isabs(dir): + dir = os.path.join(self.install_dir, dir) + elif self.root: + dir = change_root(self.root, dir) + + if f[1] == []: + # If there are no files listed, the user must be + # trying to create an empty directory, so just ignore + # it. + # Should we scream in this case? + continue + + # Check files one by one. + # Use revers order for safe removal + for j in range(len(f[1])-1, -1, -1): + data=f[1][j] + data = convert_path(data) + if not os.path.isfile(data): + # Again skip dirs. + continue + dst = os.path.join(dir, os.path.basename(data)) + if not os.path.exists(dst): + continue + del f[1][j] + if len(f[1]) == 0: + del self.data_files[i] + + return install_data.run(self) setup(name = 'usher', version = '0.1', package_dir = { 'usher':'python' }, packages = ['usher', 'usher.ushercli', 'usher.usherlnm', 'usher.utils', 'usher.usherctrl'], + cmdclass = {'install_data':smart_install_data}, data_files = [ ('/etc/init.d', ['initscripts/usherctrl', 'initscripts/usherlnm']), - ('/etc/usher', ['configs/usherctrl.config', 'configs/usherlnm.config', 'configs/ushercli.config']), + ('/etc/usher', ['configs/usherctrl.config', 'configs/usherlnm.config', 'configs/ushercli.config'], "preserve"), ("/usr/lib/python%s/site-packages/usher/usherctrl" % pyver, ['python/usherctrl/app.tac']), ("/usr/lib/python%s/site-packages/usher/usherlnm" % pyver, ['python/usherlnm/app.tac']) ]

2 4

zc.buildout minitutorial at PyCon
by Jim Fulton 22 Dec '06

22 Dec '06

I'm giving a pair of mini tutorials at PyCon as a single tutorial: http://us.pycon.org/TX2007/TutorialsAM#AM7 One of these is on zc.buildout. This will be a good opportunity to learn about zc.buildout. It will also be a good opportunity to get an introduction to creating eggs. I've included the outline for the buildout mini tutorial below. You can sign up for the tutorial when you register for PyCon: http://us.pycon.org/TX2007/Registration The other mini tutorial is on the Zope Component Architecture. It is aimed a Python programmers in general. You needed be or intend to be a Zope developer to benefit from it. Jim Introduction to zc.buildout - Why zc.buildout? - System assembly - why not make or scons? - Python application assembly with eggs - Support for developers - Assembling applications versus installing packages - Why not easy_install? - A Python Egg Primer Here I'll provide an introduction to using eggs from the point of view of a the lazy programmer. I'll omit setuptools arcana and focus on the core concepts that make eggs so useful. - Eggs They can sound complicated, but they are actually pretty simple. - easy_install and setuptools - Some egg-related jargon - distributions - source and binary distributions - eggs and develop eggs - requirements - index- and link-servers - entry points and script generation - Quick buildout introduction - A buildout.cfg file - Parts - Recipes - Special recipes for supporting Python application development - Buildout examples - Using buildout to try out new packages - Using buildout to create a development environment - Installing egg-based scripts for personal use - System assembly - A lazy programmer's introduction to creating eggs - Develop eggs, a minimal starting point - Adding data needed for distribution - Creating distribution files - Extending buildout with new recipes - The recipe API - A sample recipe - Part dependencies - Advanced topics - Sharing an egg repository across projects - Offline mode - Multiple deployment environments (dev/stage/prod) and multiple machines. - Using buildout with system-packaging tools (e.g. RPM). -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

1 1

workingenv: always installs setuptools?
by Jean Jordaan 17 Dec '06

17 Dec '06

Hi there In install_setuptools I read: "(only called if setuptools is not installed on the system)". However, the only call to install_setuptools is unconditional, and it wants to install a local copy of setuptools although I have it installed. Which is wrong, the docstring or the code? This is with revision 2128. -- jean . .. .... //\\\oo///\\

2 1