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

Newbie questions about setuptools
by Edward Ream 16 Jul '07

16 Jul '07

I have some questions and comments about setuptools and easy_install. What I like best about setuptools is that setup eliminates the need to maintain manifest.in and MANIFEST files. Assuming that everything in the cvs tree is part of the distribution is a clever idea, and it works for me. This is reason enough for me to want to use setuptools. However, I have the following problems with setuptools. These are serious enough so that for now I just use setuptools to create .zip files. 1. On both XP and Ubuntu, running python setup.py bdist_egg gives a .egg file with a suffix of py2.5.egg, even though the version arg to setup is '4.4.3preview9' I was expecting a suffix of all.egg, because platforms = ['all',] Can anyone explain what is going on? Here is the complete call to setup: setuptools.setup ( name='leo', version='4.4.3preview9', author='Edward K. Ream', author_email='edreamleo(a)charter.net', url='http://webpages.charter.net/edreamleo/front.html', download_url='http://downloads.sourceforge.net/leo/leo-4.4.3preview9.egg', packages = setuptools.find_packages(), include_package_data = True, exclude_package_data = { '': ['*.pyc','*.pyo']}, zip_safe=False, install_requires=[], description = 'Leo: Literate Editor with Outlines', license='Python', platforms=['all',], long_description = long_description, keywords = 'outline, outliner, ide, editor, literate programming', ) 2. The resulting egg file is much larger than the .zip file created by 'python setup.py sdist' in spite of exclude_package_data = { '': ['*.pyc','*.pyo']}, Is there any way to exclude .pyc and .pyo files? 3. 'python setup.py register' works fine, but 'python setup.py upload' fails with an 'invalid request' returned from the server. Maybe because the egg is over 8Meg? 4. 'easy_install leo' is supposed to use the download_url link arg. This is a great idea. Alas, for me it is spoiled by the setuptools pre/post release naming convention. The problem is that this convention is applied to all the links on the download_url page. Because I can't upload to the Python Cheese Shop, I used Leo's SourceForge download page for the main Leo project. The setup.py script is supposed to find the latest release on the page, but setup.py thinks that the latest match is something like Leo-4.2.1.zip (!!) This in spite of the fact that Leo-4.4.3rc1.zip exists on the page. I can't change the filenames on Leo's SourceForge page, and I can't change setuptools's naming conventions. How is 'easy_install leo' going to find the proper version? 5. setuptools is advertised as an 0.x release. This post appeared over a year ago, http://bitworking.org/news/Please_stop_using_setuptools__at_least_exclusive… This post may be obsolete, but it troubles me. I suppose I wouldn't worry so much were it not for these other issues. Any help would be greatly appreciated. Thanks. Edward -------------------------------------------------------------------- Edward K. Ream email: edreamleo(a)charter.net Leo: http://webpages.charter.net/edreamleo/front.html --------------------------------------------------------------------

5 16

Missing options for setuptools develop
by Jamie Kirkpatrick 02 Jul '07

02 Jul '07

Couple of things. Currently there is no way to pass custom options through setuptools "develop" to distutils build_ext. What this means in practice is that you cannot do the following things: • pass the --debug flag to build_ext so as to have your module build against debug libraries. • pass any of the SWIG options through. • I'm sure there are other limitations. Because of this I ended up abandoning the swig functionality of distutils and running that as a pre distuils phase of my build scripts - it would be better If I could use it through distutils though. The show stopper is the fact I can't build against debug libraries - this means I cannot mix the --debug type builds and the develop functionality, something that seems like a logical thing to do. Is there any chance that someone could find a way to allow options to be passed through to build_ext as it is run? I'm sure its just a case of adding another option to setuptools develop and then passing it through at the relevant point. If noone wants to take it on I'm happy to write a patch if we all agree its the way to go. Thanks in advance Jamie

3 3

Performance implications of having large numbers of eggs?
by Dave Peterson 02 Jul '07

02 Jul '07

Has anyone done any investigation into the performance implications of having large numbers of eggs installed? Is there any sort of performance hit? It seems to me that having a really large path might slow down imports a bit, though I suspect this is in C code so probably not a significant problem. It also seems like there might be some startup penalties due to the overhead of setting up the path when using eggs, but this is a one-time cost during python startup, so probably not too bad either. I'm asking because we're in the process to switching our open-source Enthought Tool Suite library to a distribution of components via eggs and we're having some internal debate as to whether we need to minimize the number of eggs or not. It definitely seems nice to have smaller subsets of functionality -- from the point of being able to make things stable, managing their APIs, managing cross-component dependencies, and from the user update size viewpoint. But are we paying a performance penalty for going too small in scope with our eggs? -- Dave

4 4

Re: [Distutils] setuptools, how to read metadata programatically?
by Phillip J. Eby 30 Jun '07

30 Jun '07

At 02:02 PM 6/30/2007 -0400, Jorge Vargas wrote: >hi > >I'm building a plugin manager on top of setuptools and I'll like to >know how could I read the package metadata if I got it's EntryPoint. Use entrypoint.dist.get_metadata('PKG-INFO') to get the PKG-INFO file as a string. See the PKG-INFO format PEPs to understand what's in there. Use entrypoint.dist.version to get the version, without needing to parse PKG-INFO. (Well, it may get parsed for you, if it's a "develop" egg. But the point is, you don't need to explicitly mess with PKG-INFO unless you want to get other data than the version.) >basically what I need is get the author, version,etc. I found a >pkg_resources.EggMetadata but i'm not sure how to instantiate it >because I don't know what a "importer" means in this context. You don't need to instantiate those metadata classes; that's done for you automatically by functions like 'find_distributions()'. The entrypoint.dist attribute will give you a distribution with the right type of metadata already attached. Likewise, distribution objects obtained from a WorkingSet or Environment will be properly initialized as well.

2 1