Mailman 3 May 2007 - 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

unicode bug in distutils
by Tarek Ziadé 05 Apr '09

05 Apr '09

Hello, I have created a setup.py file for distirbution and I bumped into a small bug when i tried to set my name in the contact field (Tarek Ziadé) Using string (utf8 file): setup( maintainer="Tarek Ziadé" ) leads to: File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/distutils/command/register.py", line 162, in send_metadata auth) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/distutils/command/register.py", line 257, in post_to_server value = unicode(value).encode("utf-8") UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 10: ordinal not in range(128) Using unicode: setup( maintainer=u"Tarek Ziadé" ) leads to: File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/distutils/dist.py", line 1094, in write_pkg_file file.write('Author: %s\n' % self.get_contact() ) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 18: ordinal not in range(128) I would propose a patch for this problem but i don't know what would be the best input (i guess unicode for names) Regards Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

6 9

Adventures with x64, VS7 and VS8 on Windows
by Mark Hammond 22 Mar '08

22 Mar '08

Hi all, I hope the cross-post is appropriate. I've started playing with getting the pywin32 extensions building under the AMD64 architecture. I started building with Visual Studio 8 (it was what I had handy) and I struck a few issues relating to the compiler version that I thought worth sharing. * In trying to build x64 from a 32bit VS7 (ie, cross-compiling via the PCBuild directory), the python.exe project fails with: pythoncore fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'AMD64' is this a known issue, or am I doing something wrong? * The PCBuild8 project files appear to work without modification (I only tried native compilation here though, not a cross-compile) - however, unlike the PCBuild directory, they place all binaries in a 'PCBuild8/x64' directory. While this means that its possible to build for multiple architectures from the same source tree, it makes life harder for tools like 'distutils' - eg, distutils already knows about the 'PCBuild' directory, but it knows nothing about either PCBuild8 or PCBuild8/x64. A number of other build processes also know to look inside a PCBuild directory (eg, Mozilla), so instead of formalizing PCBuild8, I think we should merge PCBuild8 into PCBuild. This could mean PCBuild/vs7 and PCBuild/vs8 directories with the "project" files, but binaries would still be generated in the 'PCBuild' (or PCBuild/x64) directory. This would mean the same tree isn't capable of hosting 2 builds from different VS compilers, but I think that is reasonable (if it's a problem, just have multiple source directories). I understand that PCBuild8 is not "official", but in the assumption that future versions of Python will use a compiler later than VS7, it makes sense to me to clean this up now - what are others opinions on this? * Re the x64 directory used by the PCBuild8 process. IMO, it makes sense to generate x64 binaries to their own directory - my expectation is that cross-compiling between platforms is a reasonable use-case, and we should support multiple achitectures for the same compiler version. This would mean formalizing the x64 directory in both 'PCBuild' and distutils, and leaving other external build processes to update as they support x64 builds. Does this make sense? Would this fatally break other scripts used for packaging (eg, the MSI framework)? * Wide characters in VS8: PC/pyconfig.h defines PY_UNICODE_TYPE as 'unsigned short', which corresponds with both 'WCHAR' and 'wchar' in previous compiler versions. VS8 defines this as wchar_t, which I'm struggling to find a formal definition for beyond being 2 bytes. My problem is that code which assumes a 'Py_UNICODE *' could be used in place of a 'WCHAR *' now fails. I believe the intent on Windows has always been "PyUNICODE == 'native unicode'" - should PC/pyconfig.h reflect this (ie, should pyconfig.h grow a version specific definition of PyUNICODE as wchar_t)? * Finally, as something from left-field which may well take 12 months or more to pull off - but would there be any interest to moving the Windows build process to a cygwin environment based on the existing autoconf scripts? I know a couple of projects are doing this successfully, including Mozilla, so it has precendent. It does impose a greater burden on people trying to build on Windows, but I'd suggest that in recent times, many people who are likely to want to build Python on Windows are already likely to have a cygwin environment. Simpler mingw builds and nuking MSVC specific build stuff are among the advantages this would bring. It is not worth adding this as "yet another windows build option" - so IMO it is only worth progressing with if it became the "blessed" build process for windows - if there is support for this, I'll work on it as the opportunity presents itself... I'm (obviously) only suggesting we do this on the trunk and am happy to make all agreed changes - but I welcome all suggestions or critisisms of this endeavour... Cheers, Mark

14 66

buildout, zc.recipe.testrunner and tests_require
by Nathan R. Yergler 15 Nov '07

15 Nov '07

I'm using zc,buildout to manage the development of a very simple web application. I'd like to have a simple test runner that runs my doctests, but have run into a slight problem. I'm using wsgi_intercept to aid in testing, but unfortunately wsgi_intercept isn't a proper Python package ("yet", according to Titus). So I have a package-i-fied version in my svn repository and in my buildout.cfg I specify: develop = . ./wsgi_intercept_ I initially was using the "interpreter" option to get a Python interpreter with my eggs on the path, and running "./bin/python setup.py test". That, however, required me to list wsgi_intercept as a package requirement, when I really want to list it as a testing requirement. Moving it to a testing requirement caused it's develop egg not to be on the PYTHONPATH, so setuptools tries to find it. Which it couldn't. I tried using zc.recipe.testbrowser, thinking that maybe it'd look at the tests_require for the target eggs, but no such luck. The testrunner also seems pretty promiscuous in looking for things to test (it tries to import my eggs directory and test them which predictably doesn't work), but that's another story. So... any suggestions on using zc.buildout along with testing dependencies (generally or with zc.recipe.testrunner)? Thanks, Nathan

4 4

slow Python startup with a couple of easy_install-ed packages
by Thomas Heller 17 Jun '07

17 Jun '07

Well, easy_install makes it snap to install packages that I may or may not use. Nothing is easier than to 'easy_install something-recently-announced', even if I never will use it (after a preliminary look). Often I forget to uninstall the packages again, or promise to do that later. Disk space is cheap. However, I found that with the ~20 eggs that I have installed the startup time of the Python interpreter (Python2.5, WinXP, measured with 'timeit python -c ""') rises considerably - 2.5 times slower. This only occurs when the eggs are listed in the easy_install.pth file; if they are moved into a 'normal' pth file this slowdown does not occur, although I can still import the eggs fine. I assume the additional time is spent by setuptools looking up entry points or whatever? And that this additional processing is not needed for the eggs that do not provide entry points? Or are not *using* setuptools themselves? If this is true, wouldn't it be possible to skip the processing for those eggs? IMO this is a critical problem of easy_install... (Imaging how the installed and possibly never used eggs pile up). Thomas

3 3

setuptools 0.6c6 released
by Phillip J. Eby 31 May '07

31 May '07

I've uploaded a new release version of setuptools, 0.6c6, which fixes a number of outstanding problems. Please note that the following issues are *not* yet fixed: * "bdist_wininst upload" on Python 2.5 sometimes tries to upload the .exe twice * platform-specific eggs don't take precedence over non-platform-specific ones * error checking of regular+namespace packages isn't sufficient (you can still specify silly things and get silly results) * data files specifed only via package_data may not be included in a generated sdist This is probably not a complete list, either. I've got a much longer TODO list, but most of the rest are more like "quirks" than bugs.

1 0

Re: [Distutils] I need to create a customized Fedora live cd with Python applications on it
by Stanley A. Klein 30 May '07

30 May '07

On 4/24/07, "Nathan R. Yergler" <nathan at yergler.net> wrote: >On 4/24/07, Stanley A. Klein <sklein at cpcug.org> wrote: >> I need to create a customized Fedora live CD with Python applications on >> it. The live CD requires rpm's of the applications. (The issues are >> similar to a customized Ubuntu live CD but Ubuntu requires deb's.) >> >> It seems that the distutils/setup.py functions that create rpms are >> broken. I get errors most of the time that I try to use them. The >Python >> community seems to be focused on eggs, that are useful if individually >> installed but don't match the distribution formats of the Linux distros. >> Those distribution formats are what the distros use for their live CD's. >I've successfully created RPMs many times in the past; can you >elaborate on the problems you're having? >> >> Is there a way to convert eggs to rpm's? Can the distutils be fixed to >> reliably create rpm's? Is there some other way to install eggs on distro >> customized live CD's? >If it's a live CD, is there a reason you can't just put them into >site-packages on the CD filesystem? (I have no idea what goes into >building a Fedora live CD, so "yes, there's a reason" is a sufficient >answer). Below is a typical example of the problem I encounter. I tried to build an RPM of ZSI-2.0 using "python setup.py bdist_rpm", and got the output below at the end. Most of the time I have the same problem trying to create RPM's from python tar.gz files. The reason you can't just put the files into site-packages on the CD file system (AFAIK for either Fedora or a Debian derivative such as Ubuntu) is that the live CD builds its system from packages in the distro format. To get files into site-packages as part of the live CD, they have to be loaded there from an RPM or deb format package. I don't know of any way the live CD's can be set up to handle eggs. Also, the live CD's are now being made installable, so if the user wants to do so, installing from the live CD is an option. The installers expect distro formatted packages. Stan Klein ---------------------------------------------------------------------- error: Installed (but unpackaged) file(s) found: /usr/lib/python2.4/site-packages/ZSI/ServiceContainer.pyo /usr/lib/python2.4/site-packages/ZSI/ServiceProxy.pyo /usr/lib/python2.4/site-packages/ZSI/TC.pyo /usr/lib/python2.4/site-packages/ZSI/TCapache.pyo /usr/lib/python2.4/site-packages/ZSI/TCcompound.pyo /usr/lib/python2.4/site-packages/ZSI/TCnumbers.pyo /usr/lib/python2.4/site-packages/ZSI/TCtimes.pyo /usr/lib/python2.4/site-packages/ZSI/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/address.pyo /usr/lib/python2.4/site-packages/ZSI/auth.pyo /usr/lib/python2.4/site-packages/ZSI/client.pyo /usr/lib/python2.4/site-packages/ZSI/digest_auth.pyo /usr/lib/python2.4/site-packages/ZSI/dispatch.pyo /usr/lib/python2.4/site-packages/ZSI/fault.pyo /usr/lib/python2.4/site-packages/ZSI/generate/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/generate/commands.pyo /usr/lib/python2.4/site-packages/ZSI/generate/containers.pyo /usr/lib/python2.4/site-packages/ZSI/generate/pyclass.pyo /usr/lib/python2.4/site-packages/ZSI/generate/utility.pyo /usr/lib/python2.4/site-packages/ZSI/generate/wsdl2dispatch.pyo /usr/lib/python2.4/site-packages/ZSI/generate/wsdl2python.pyo /usr/lib/python2.4/site-packages/ZSI/parse.pyo /usr/lib/python2.4/site-packages/ZSI/resolvers.pyo /usr/lib/python2.4/site-packages/ZSI/schema.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/WSresource.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/WSsecurity.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/client.pyo /usr/lib/python2.4/site-packages/ZSI/typeinterpreter.pyo /usr/lib/python2.4/site-packages/ZSI/version.pyo /usr/lib/python2.4/site-packages/ZSI/writer.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/Namespaces.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/TimeoutSocket.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/UserTuple.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/Utility.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/WSDLTools.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/XMLSchema.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/XMLname.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/c14n.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/logging.pyo RPM build errors: File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/PKG-INFO File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/SOURCES.txt File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/dependency_links.txt File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/entry_points.txt File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/requires.txt File listed twice: /usr/lib/python2.4/site-packages/ZSI-2.0-py2.4.egg-info/top_level.txt Installed (but unpackaged) file(s) found: /usr/lib/python2.4/site-packages/ZSI/ServiceContainer.pyo /usr/lib/python2.4/site-packages/ZSI/ServiceProxy.pyo /usr/lib/python2.4/site-packages/ZSI/TC.pyo /usr/lib/python2.4/site-packages/ZSI/TCapache.pyo /usr/lib/python2.4/site-packages/ZSI/TCcompound.pyo /usr/lib/python2.4/site-packages/ZSI/TCnumbers.pyo /usr/lib/python2.4/site-packages/ZSI/TCtimes.pyo /usr/lib/python2.4/site-packages/ZSI/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/address.pyo /usr/lib/python2.4/site-packages/ZSI/auth.pyo /usr/lib/python2.4/site-packages/ZSI/client.pyo /usr/lib/python2.4/site-packages/ZSI/digest_auth.pyo /usr/lib/python2.4/site-packages/ZSI/dispatch.pyo /usr/lib/python2.4/site-packages/ZSI/fault.pyo /usr/lib/python2.4/site-packages/ZSI/generate/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/generate/commands.pyo /usr/lib/python2.4/site-packages/ZSI/generate/containers.pyo /usr/lib/python2.4/site-packages/ZSI/generate/pyclass.pyo /usr/lib/python2.4/site-packages/ZSI/generate/utility.pyo /usr/lib/python2.4/site-packages/ZSI/generate/wsdl2dispatch.pyo /usr/lib/python2.4/site-packages/ZSI/generate/wsdl2python.pyo /usr/lib/python2.4/site-packages/ZSI/parse.pyo /usr/lib/python2.4/site-packages/ZSI/resolvers.pyo /usr/lib/python2.4/site-packages/ZSI/schema.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/WSresource.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/WSsecurity.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/twisted/client.pyo /usr/lib/python2.4/site-packages/ZSI/typeinterpreter.pyo /usr/lib/python2.4/site-packages/ZSI/version.pyo /usr/lib/python2.4/site-packages/ZSI/writer.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/Namespaces.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/TimeoutSocket.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/UserTuple.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/Utility.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/WSDLTools.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/XMLSchema.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/XMLname.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/__init__.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/c14n.pyo /usr/lib/python2.4/site-packages/ZSI/wstools/logging.pyo error: command 'rpmbuild' failed with exit status 1

4 11

distutils.core.setup: ImportError: undefined symbol: g_free
by Thomas 27 May '07

27 May '07

Hallo, I want to call some C functions from the gnome-panel source. setup.py: > setup(name = "calwrap", version = "1.0", ext_modules = [ ... Then I call: ./setup.py build Compiling works fine, I get: calwrap.so Then in python I get the following error: > Python 2.5.1 (r251:54863, May 2 2007, 16:56:35) > [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import calwrap > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ImportError: ./calwrap.so: undefined symbol: g_free I tried: > extra_link_args = ["-Xlinker", "-export-dynamic"] Any ideas? fg Thomas

1 0