Mailman 3 April 2008 - Distutils-SIG

Upgrading dependencies
by Charlie Moad 29 Apr '18

29 Apr '18

Is it currently possible to upgrade dependencies as well when upgrading a packages? If not, this would be a really nice feature to add to easy_install. Maybe a call like: easy_install --upgrade --upgrade-deps Package Obviously it makes sense to leave this off by default. Thanks, Charlie

2 1

Changes to --find-links and --upgrade in SVN
by Phillip J. Eby 29 Apr '18

29 Apr '18

Elvelind Grandin reported a problem with the "develop" command that turned out to be a flaw in its --find-links support. Specifically, it wasn't ever processing the links. :) In the process of fixing it, I wound up cleaning up an annoying (to me, at least) quirk of the previous workings of --find-links. It used to be that find-links would always be processed first, no matter what, even if you were doing a completely local operation. This would've been especially annoying if it carried over into "develop", so I made some changes. Now, if an item passed to --find-links is local (a filename or file: URL), or a direct link to an egg or other distribution, it is indexed immediately. Remote URLs are now only retrieved if a dependency can't be resolved locally, or if you use the -U or --upgrade options (this goes for "develop" too). Note that this is a behavior change for easy_install, which was effectively treating --find-links as though you'd specified --upgrade in certain cases. So, if you're used to getting upgrades downloaded as a result of using --find-links, please note that this will no longer happen. EasyInstall will now *only* go online if a dependency can't be resolved locally, if -U or --upgrade is used, or if you provided suitable direct URLs via an argument or --find-links, or via a link in a local .html file.

2 1

Problems with svn in windows
by Sharky On PTNet 29 Apr '18

29 Apr '18

Hi, I´m trying to do "easy_install setuptools==dev" in a windows box but have an error with svn command. """... 'svn' is not recognized as an internal or external command, ...""" I have installed TortoiseSVN but it seems that don't have command line, is all with the Explorer. Can you tell me what client I may use in windows? Thanks for all, Helio Pereira Sharky @ PTNet

3 2

local development scenarios
by tgreenwood 29 Apr '18

29 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm new to distutils/and the egg system. I have not researched the archives as much as I should, so please excuse me if this is familiar territory... Q: Is it possible for dependency checks to work for non pipy deployed eggs? - A.egg - B.egg (setup_requires and install_requires A.egg) - email A and B eggs to friend - tell friend to : easy_install B - but B.egg does not install A...in fact, in my test case, it fails b/c it cannot find A in pipy - in this example, what happens if friend does not have net connection on target machine? how can they install from the eggs alone and get the dep checking to work? Q: How does my friend run the unittests on the egg that they have just installed? As I am developing, I frequently run the unittests and after every bdist_egg build, I also run the unit tests that way, too. How can the consumer do the same? Q: One of my apps is a command line app, say foo.py is a command line app that takes arg1, arg2,... How can the user run this app when it is encased in an egg? Q: How do I define my own pipy? While I like the idea of deploying there for the overall community, I don't want to send my half baked code into the wild. But I'd like to try the general functionality of having a deploy site for my beta customers. How can I set this up? Thanks in advance. - -Todd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDl9Hfz6uXX4lQc/URAnY4AJ47DFHL/cpEltmqoUyGqzhsK5FjRACgt01v akc3Wh3IOXVv2jiS8TszhuE= =Rv/x -----END PGP SIGNATURE-----

5 12

Choice of dependencies?
by John J Lee 29 Apr '18

29 Apr '18

Is it possible for a package to depend on one of several packages, with the user having the option to pick? For example, my package P might depend on package A, plus either package B or package C. I know I could (ab)use extras_require, but in my case this is a real dependency rather than an optional extra. The other option I have is to just pick one of the dependencies (B or C in my example above), and thereby force people to install it even though it's not strictly required. Neither option seems particularly attractive. John

3 6

setuptools doc patch
by John J Lee 29 Apr '18

29 Apr '18

The comma removed by the patch below implies that users working from a Subversion checkout should not use EasyInstall to periodically fetch the latest version. That's not what you intended to say, I assume? http://peak.telecommunity.com/DevCenter/setuptools You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to +are working from a Subversion checkout rather than using EasyInstall to periodically fetch the latest version. Hmm, probably much better than the patch above: -You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to -periodically fetch the latest version. +If your users are working from a Subversion checkout rather than using +EasyInstall, you should also inform them of the need to run this command +to periodically fetch the latest version. John

2 2

Re: [Distutils] distutils install probs on suse 9.0
by Mats Wichmann 29 Apr '18

29 Apr '18

At 05:43 AM 5/18/2004, David Handy wrote: >On Tue, 18 May 2004, Floris van der Tak wrote: > >> my attempt to install the distutils on suse 9.0 (which provides python >> 2.3) fails: > >Why are you installing distutils on a system that already has Python 2.3 >installed? Python 2.3 normally comes with distutils as part of the Python >standard library. > >Did suse distribute a version of Python that had distutils removed? It should come from python-devel

2 1

Sample setup.py for Numeric Python
by Greg Ward 29 Apr '18

29 Apr '18

Hi again -- [cc'd to Paul Dubois: you said you weren't following the distutils sig anymore, but this directly concerns NumPy and I'd like to get your input!] here's that sample setup.py for NumPy. See below for discussion (and questions!). ------------------------------------------------------------------------ #!/usr/bin/env python # Setup script example for building the Numeric extension to Python. # This does sucessfully compile all the .dlls. Nothing happens # with the .py files currently. # Move this file to the Numerical directory of the LLNL numpy # distribution and run as: # python numpysetup.py --verbose build_ext # # created 1999/08 Perry Stoll __rcsid__ = "$Id: numpysetup.py,v 1.1 1999/09/12 20:42:48 gward Exp $" from distutils.core import setup setup (name = "numerical", version = "0.01", description = "Numerical Extension to Python", url = "http://www.python.org/sigs/matrix-sig/", ext_modules = [ ( '_numpy', { 'sources' : [ 'Src/_numpymodule.c', 'Src/arrayobject.c', 'Src/ufuncobject.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/numpy.def' } ), ( 'multiarray', { 'sources' : ['Src/multiarraymodule.c'], 'include_dirs' : ['./Include'], 'def_file': 'Src/multiarray.def' } ), ( 'umath', { 'sources': ['Src/umathmodule.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/umath.def' } ), ( 'fftpack', { 'sources': ['Src/fftpackmodule.c', 'Src/fftpack.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/fftpack.def' } ), ( 'lapack_lite', { 'sources' : [ 'Src/lapack_litemodule.c', 'Src/dlapack_lite.c', 'Src/zlapack_lite.c', 'Src/blas_lite.c', 'Src/f2c_lite.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/lapack_lite.def' } ), ( 'ranlib', { 'sources': ['Src/ranlibmodule.c', 'Src/ranlib.c', 'Src/com.c', 'Src/linpack.c', ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/ranlib.def' } ), ] ) ------------------------------------------------------------------------ First, what d'you think? Too clunky and verbose? Too much information for each extension? I kind of think so, but I'm not sure how to reduce it elegantly. Right now, the internal data structures needed to compile a module are pretty obviously exposed: is this a good thing? Or should there be some more compact form for setup.py that will be expanded later into the full glory we see above? I've already made one small step towards reducing the amount of cruft by factoring 'include_dirs' out and supplying it directly as a parameter to 'setup()'. (But that needs code not in the CVS archive yet, so I've left the sample setup.py the same for now.) The next thing I'd like to do is get that damn "def_file" out of there. To support it in MSVCCompiler, there's already an ugly hack that unnecessarily affects both the UnixCCompiler and CCompiler classes, and I want to get rid of that. (I refer to passing the 'build_info' dictionary into the compiler classes, if you're familiar with the code -- that dictionary is part of the Distutils extension-building system, and should not propagate into the more general compiler classes.) But I don't want to give these weird "def file" things standing on the order of source files, object files, libraries, etc., because they seem to me to be a bizarre artifact of one particular compiler, rather than something present in a wide range of C/C++ compilers. Based on the NumPy model, it seems like there's a not-too-kludgy way to handle this problem. Namely: if building extension "foo": if file "foo.def" found in same directory as "foo.c" add "/def:foo.def" to MSVC command line this will of course require some platform-specific code in the build_ext command class, but I figured that was coming eventually, so why put it off? ;-) To make this hack work with NumPy, one change would be necessary: rename Src/numpy.def to Src/_numpy.def to match Src/_numpy.c, which implements the _numpy module. Would this be too much to ask of NumPy? (Paul?) What about other module distributions that support MSVC++ and thus ship with "def" files? Could they be made to accomodate this scheme? Thanks for your feedback -- 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

4 5

Can now compile simple extensions
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I found the time to hack in the ability to compile extension modules to the Distutils. Mainly, this meant adding a 'build_ext' command which uses a CCompiler instance for all its dirty work. I also had to add a few methods to CCompiler (and, of course, UnixCCompiler) to make this work. And I added a new module, 'spawn', which takes care of running sub-programs more efficiently and robustly (no shell involved) than os.system. That's needed, obviously, so we can run the compiler! If you're in the mood for grubbing over raw source code, then get the latest from CVS or download a current snapshot. See http://www.python.org/sigs/distutils-sig/implementation.html for a link to the code snapshot. I'm still waiting for more subclasses of CCompiler to appear. At the very least, we're going to need MSVCCompiler to build extensions on Windows. Any takers? Also, someone who knows the Mac, and how to run compilers programmatically there, will have to figure out how to write a Mac-specific concrete CCompiler subclass. The spawn module also needs a bit of work to be portable. I suspect that _win32_spawn() (the intended analog to my _posix_spawn()) will be easy to implement, if it even needs to go in a separate function at all. It looks from the Python Library documentation for 1.5.2 that the os.spawnv() function is all we need, but it's a bit hard to figure out just what's needed. Windows wizards, please take a look at the 'spawn()' function and see if you can make it work on Windows. As for actually compiling extensions: well, if you can figure out the build_ext command, go ahead and give it a whirl. It's a bit cryptic right now, since there's no documentation and no example setup.py. (I have a working example at home, but it's not available online.) If you feel up to it, though, see if you can read the code and figure out what's going on. I'm just hoping *I'll* be able to figure out what's going on when I get back from the O'Reilly conference next week... ;-) Enjoy -- 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

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

Re: [Distutils] how to easily consume just the parts of eggs that are good for you
by Stanley A. Klein 09 Oct '09

09 Oct '09

On Wed, April 9, 2008 10:05 pm, Greg Ewing <greg.ewing(a)canterbury.ac.nz> wrote: > Message: 4 > Date: Thu, 10 Apr 2008 12:59:39 +1200 > From: Greg Ewing <greg.ewing(a)canterbury.ac.nz> > Subject: Re: [Distutils] how to easily consume just the parts of eggs > that are good for you > To: distutils-sig(a)python.org > > Paul Moore wrote: > >> I believe that Mac OS X goes for an even simpler structure - >> applications store *everything* in the one directory, so that >> install/uninstall is simply a directory copy/remove. > > Yep, and thereby cuts the whole gordian knot, throws the > pieces on the fire and burns them. :-) > > Package managers have always seemed to me to be an > excessively complex solution to a problem that needn't > have existed in the first place. > > I keep hoping that someday Linux will support something > like MacOSX application bundles and frameworks, but I > haven't seen any sign of it yet. > I think this discussion arises because the operating systems we are dealing with are based on very different concepts. Windows and Mac are fundamentally single user systems that have added capabilities for multiple users and are intended to be used with proprietary software. Those considerations lead to minimal dependencies among packages (each proprietary provider needs to control its own package, except for the OS), individual users serving as their own sysadmins, and similar factors. Any dependencies in the proprietary software are hidden from the user because the provider has compiled the dependencies into the binary code they supply. Unix/Linux are fundamentally multi-user systems with a distinct role for a sysadmin. Linux and the BSD's are intended to be used with Free/Open Source Software (FOSS), and Unix originated the Software Tools concept in which individual, relatively simple, separately-developed tools are combined to perform complex tasks. Both FOSS and the Software Tools concept encourage dependencies. The need for package managers arises out of the Unix FHS. If you look at the FHS, it is clearly designed to simplify the job of the sysadmin in a multi-user system that uses FOSS and Software Tools. For example, deciding what to backup and how often to do it in a Unix/Linux system is relatively easy for the sysadmin. All the installed software is in certain top-level directories. All the config files are in /etc. All the logs. caches, spools, web pages, process locks, and certain other data are in /var. All the user data is in /home or its sysadmin-determined equivalents. If the sysadmin needs space, deleting files in /tmp will not cause a problem. In summary, Python is being used on systems that have very different underlying OS use cases. To some extent, the natural use case for Python is closest to that of Linux/Unix. Running Python on Windows/Mac requires adapting for those platforms some of the kinds of tools that simplify operations on Linux/Unix systems. This discussion is essentially about how far that goes, how to accomplish it, and how to remain compatible with the existing tools on Linux/Unix. Stan Klein

4 4

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

Unicode in distutils meta-data
by Tarek Ziadé 03 Sep '08

03 Sep '08

Hello, I would like to summarize here http://bugs.python.org/issue2562. Currently, distutils does not allows the usage of Unicode for some meta-data fields that should be able to use it. These fields are: - author - maintainer - description - long_description For instance, if you use u"Barnabé" in the author field, the DistributionMetada.write_pkg_file will fail when it tries to serialize the information into a file. The problem is that the current implementation makes the assumption that all fields are ascii string. This won't be a problem in Python 3k, of course, but currently concerns the 2.x series. One possible solution would be to move these fields to Unicode for the 2.6 series. In the meantime, many people are using str type for those fields, so as Martin mentioned, a backward compatibility would be better to support either plain string either Unicode. Other fields should be left imho in ascii, since an url for instance has to be ascii. But maybe it would be better, as Martin mentioned, to use Unicode for all fields. In any case, if we do use Unicode for some fields, we will need to provide the codec to be used to serialize the data in a file. My proposal here would be to add a 'encoding' field in the metadata that defaults to 'utf8', and that would let people explicitely indicates the encoding. I have written a quick patch here of a possible implementation, so you can see the problem : http://bugs.python.org/file9967/unicode.metadata.patch Regards, Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

2 2

[PATCH][setuptools] Add test_runner support to setup
by Klaus Zimmermann 22 Aug '08

22 Aug '08

Hi all, for our nightly build system I needed the capability to use a different test runner, namely one that outputs junit compatible xml files. In order to support that through the setup.py test command I hacked on setuptools. Is there a simpler way to do this? If not you might want to consider attached patch for addition (Should be against latest svn.) Cheers, Klaus

4 7

buildout: setting envirionment variables for zc.recipe.egg:custom?
by Christian Zagrodnick 24 Jun '08

24 Jun '08

Hi, building lxml requires additional configuration so it finds xslt-config correctly. One possibility is to set the PATH environment variable. The other is to call setup.py --xslt-config=... Using setup.py --xslt-config doesn't fit at all into buildout i think. Setting environment variables before installing an egg on the other hand might be useful. Would it make sense to put this into zc.recipe.egg or would it be better to create some unrelated recipe which only sets envirionment variables? Regards, -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

3 5

Re: [Distutils] shebang line modified by setuptools
by Phillip J. Eby 07 May '08

07 May '08

At 09:07 PM 4/11/2008 -0700, Cliff Wells wrote: >Hi Phillip, > >I recently upgraded a hosting server from Python 2.4 to Python 2.5. >Many of the sites on this server couldn't easily be upgraded to 2.5 (at >least not in a timely fashion), so my interim solution was to simply >symlink ~/bin/python -> /usr/bin/python2.4 (~/bin is first in the user's >PATH). This worked swimmingly except for applications which relied on >Paste (I should note I use the method outlined here: >http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installat…). > >The reason the Paste apps had an issue is because apparently setuptools >modifies the shebang line of paster to be "#!/usr/bin/python". This >hardcoded path overrides any PATH settings. I understand that this is >done at the time Paste is installed to tie it to the installed version >of Python. This makes sense, except that it doesn't do what it's >intended to when Python is upgraded (/usr/bin/python is no longer the >version it was installed with). > >It seems the correct solution to this is to use "#!/usr/bin/env >python" (or rather, evaluate `which env` to account for some systems >which have /bin/env rather that /usr/bin/env) which allows the sys admin >to override the Python binary much more easily. No, it isn't the correct solution. The correct solution is to re-run easy_install on the target -- it will leave the existing installed code in place, but regenerate the scripts with headers pointing to the currently-in-use Python. Even that is often not as good an idea as reinstalling for a new version of Python; some packages (notably, setuptools itself, but I have others) include different code and data depending on the Python version they are built for. For example, a package built for Python 2.5 might not include dependency specs for ctypes, sqlite, or wsgiref, but the same package might need to specify those dependencies on earlier versions of Python. By the way, please don't send me unsolicited private emails about setuptools unless you're a client or potential client. There's a reason that every single official web page about setuptools directs you to email the distutils-sig. I don't do private email for ANY of my open source projects, unless you're a client or looking to be one. Mailing lists have searchable archives, meaning that my time answering a question is being offset by its potential utility to a much larger audience. Thanks.

14 66

setuptools on 64 bit Windows broken?
by Jeroen Ruigrok van der Werven 02 May '08

02 May '08

[Apologies if this was discussed in the past, I did some searching but couldn't find much, but then again my attention is spread a little too thing lately.] Right now setuptools on Windows x64 with 64-bits Python 2.5 is (partially) broken. The error shown is: Cannot find Python executable C:\Python25\python.exe when running easy_install. The phrase comes from launcher.c which is compiled via MingW to cli.exe and gui.exe. Both of these are present in the setuptools repository and are 32-bits only for all I can determine (using file). I have not thoroughly checked it yet (due to being written in Unix-C, even though it's aimed at Windows), but my guess is it's using some API calls which fail on 64-bits Windows. I see there's a mingw-64 toolkit on the 'net nowadays. Has anyone tried this yet? Is it indeed an API issue? Furthermore, when creating an egg on Windows x64, it will create it with an identifier of win32, even though C code in a project is compiled with an AMD64 version of the compiler. For all I know 32-bits Windows systems will also pull down this version of the egg when given the chance. I guess this is due to Python 2.5 64 bit reporting win32 for sys.platform? So don't we miss something to properly distinguish between 64 bits Windows and 32 bits? Especially with x64 and Vista 64 on the market nowadays? Thanks for any pointers/clues... -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーンラウフロックヴァンデルウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Whoever undertakes to set himself up as judge in the field of truth and knowledge is shipwrecked by the laughter of the Gods.

2 1

Re: [Distutils] [Python-Dev] shal we redefine "module" and "package"?
by glyph＠divmod.com 01 May '08

01 May '08

On 10:53 pm, steve(a)holdenweb.com wrote: >zooko wrote: >>Unfortunately these answers aren't quite right. A "package" is >>actually a directory containing an __init__.py file, and a >>distribution is actually what you think of when you say "package" -- a >>reusable package of Python code that you can, for example, get from >>the Python package index. The fact that the Python "package" index is a place where you get "distributions" does seem a bit weird to me, but this is not necessarily a problem that can be fixed. Ambiguity is part of human language. Perhaps suggest transliterations of these terms for talking about python in lojban? :) >>1. A "module" shall henceforth be the name for either a foo.py file >>(a single-file module), or a directory with an __init__.py in it (a >>directory module). I have a less disruptive counterproposal. How about just starting to refer to directories (or "folders", or zip entries) with '__init__.py' in them as "package modules"? A package is-a module anyway. >>2. A "package" shall henceforth be the name of the thing that is >>currently called a "distribution". I belive a multi-word term here would be similarly more memorable and precise. A "package distribution" would include the more familiar term while still being specific, consistent with the old terminology, and correct. Using a qualifying word is probably a good idea in this context anyway. I usually say "debian package", "RPM", "MSI", or "tarball" unless I'm specifically talking about "packages for your platform", almost always in the phrase, "please do not use distutils to do a system install of Twisted, use the specific package for your platform". >-1 I do, however, agree with Steve emphatically on your original proposal. Changing the terminology now will make billions upon billions of Python web pages, modules (c.f. twisted.python.modules.PythonModule.isPackage()) documents, and searchable message archives obsolete, not to mention that 90% of the community will probably ignore you and use the old terminology anyway, creating more confusion than it eliminates.

3 4

Setuptools Bug: all files installed +x
by Pete 01 May '08

01 May '08

On both linux & OS X, Setuptools installs all .py/.pyc files with mode a+x (executable for all users). This occurs regardless of original the permissions in the source tarball. Doing so breaks nosetests, which by default refuses to import executable files for test-discovery purposes as a safety measure. This behavior is broken & dangerous. -- Pete pfein(a)pobox.com

6 11

shal we redefine "module" and "package"?
by zooko 01 May '08

01 May '08

Folks: Here's an experiment you can perform. Round up a Python programmer and ask him the following three questions: Q1. You type "import foo" and it works. What kind of thing is foo? Q2. You go to the Python package index and download something named "bar-1.0.0.tar.gz". What kind of thing is bar? Q3. What is a "distribution"? I'm willing to bet that you will get the following answers: A1. foo is a module. A2. bar is a package. A3. A distribution is a version of Linux that comes with a lot of Free Software. Unfortunately these answers aren't quite right. A "package" is actually a directory containing an __init__.py file, and a distribution is actually what you think of when you say "package" -- a reusable package of Python code that you can, for example, get from the Python package index. Educational efforts such as the Python tutorial and the distutils docs have not succeeded in training Python programmers to understand the terminology for these things as used by the Python implementors, so perhaps instead the implementors should start using the terminology understood by the programmers: 1. A "module" shall henceforth be the name for either a foo.py file (a single-file module), or a directory with an __init__.py in it (a directory module). 2. A "package" shall henceforth be the name of the thing that is currently called a "distribution". Regards, Zooko who doesn't mind stirring up trouble on occasion...

4 3

problems bundling data with setuptools
by Michael Hearne 30 Apr '08

30 Apr '08

I'm having trouble bundling any kind of data (non-Python code) in my egg. Here are the file contents of my source directory: hello.py (cheesy script) README.txt MANIFEST.in (has one line, "include *.txt") setup.py, which looks like: from setuptools import setup, find_packages setup( name = "HelloWorld", version = "0.1", scripts=['hello.py'], include_package_data = True ) I'm creating the egg with python setup.py bdist_egg. I would expect that README.txt should appear in the egg somewhere, but it doesn't. What am I missing? Thanks, Mike ------------------------------------------------------ Michael Hearne mhearne(a)usgs.gov (303) 273-8620 USGS National Earthquake Information Center 1711 Illinois St. Golden CO 80401 Senior Software Engineer Synergetics, Inc. ------------------------------------------------------

2 3

buildout and mod_wsgi
by Martin Aspeli 29 Apr '08

29 Apr '08

Hi all, I'm trying to deploy a Repoze-based application via mod_wsgi. I'm building Repoze in a buildout. The problem is that I need to get mod_wsgi to execute the WSGI script with buildout's working set of eggs. The mod_wsgi configuration looks like this: WSGIDaemonProcess tmp threads=1 processes=4 maximum-requests=10000 python-path=/usr/lib/python2.4/site-packages <VirtualHost *:80> ServerName my.machine.local WSGIScriptAlias / /path/to/bin/zope2.wsgi WSGIProcessGroup tmp WSGIPassAuthorization On </VirtualHost> Now, this says to create a process pool of Python processes with the given python-path. This is really geared towards the virtualenv use case, where you'd have a custom virtualenv python-path for each project. In the case of buildout, however, the pythonpath is explicitly for console scripts by munging console scripts and doing sys.path manipulation. Unfortunately, zope2.wsgi is not a console script, it's just a script that contains: from paste.deploy import loadapp ini = '/path/to/pasteconfig.ini' application = loadapp('config:%s' % ini) The key here is that this is a script that needs to define a global variable 'application'. The only way I can make this work, is to paste a block of sys.path manipulation from a console script that buildout has had the opportunity to munge, but that's not exactly a stable solution. I can see the following possible solutions: 1) Make a buildout recipe that creates a directory with a .pth file for all the eggs in the working set. This would then be able to serve as a python-path above. 2) Make a buildout recipe that generates the zope2.wsgi script as above, but also generates the sys.path munging. Does one of these exist already? Is there a better way? For reference: http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIDaemonPro… Cheers, Martin

2 2

Two versions of SQLAlchemy side-by-side?
by skip＠pobox.com 29 Apr '08

29 Apr '08

We have SQLAlchemy 0.3.3 installed via setuptools. I upgraded to 0.4.5 today but had to back that out (by editing easy-install.pth) because of API changes. Now I have these two installs .../site-packages/SQLAlchemy-0.3.3-py2.4.egg .../site-packages/SQLAlchemy-0.4.5-py2.4.egg Is there a way to import the 0.4.5 version for testing without disturbing the 0.3.3 version? I tried placing the 0.4.5 egg directory in PYTHONPATH but I still get the 0.3.3 version when I "import sqlalchemy". What's a fella to do? Thanks, Skip

3 5

Re: [Distutils] virtual env with exec prefix
by Hans Meine 28 Apr '08

28 Apr '08

Hi Ian, recently I reported this problem to you: > [...] here at our university, python (as > well as hundreds of other software packages) is installed in a shared NFS > tree with a clear separation of --prefix and --exec-prefix, i.e. all > platform-specific stuff goes into the according subdirectories. [...] > [2] meine@kogspc33:~ -> virtualenv enthought-inst > New python executable in enthought-inst/bin/python > Installing setuptools.... > Complete output from command enthought-inst/bin/python -c "#!python > \"\"\"Bootstrap setuptoo... > > > > > " /software/python-2.4.4/SuSE-10...4.egg: > error: invalid Python installation: unable to > open /software/python-2.4.4/lib/python2.4/config/Makefile (No such file or > directory) > > [The message] is right, because it should be > /software/python-2.4.4/SuSE-10.2/lib/python2.4/config/Makefile > which exists (in the SuSE-10.2 directory). I have now debugged this a little bit (using virtualenv from SVN), and it seems to be a problem with the virtualenv'd python and setuptools. I have written the EZ_SETUP_PY to disk, and when I mimick virtualenv's command for installing setuptools, I get the error: [2] meine@kogspc33:~/Programming/enthought -> inst/bin/python ../ez_setup.py -v /home/meine/Programming/virtualenv-svn/support-files/setuptools-0.6c8-py2.4.egg error: invalid Python installation: unable to open /software/python-2.4.4/lib/python2.4/config/Makefile (No such file or directory) (NB: inst is the virtual env) OTOH, when I run this with the python binary from its original location, it works fine. Since the error comes from deep within setuptools (AFAICS), should this be discussed on distutils-sig? Ciao, / / /--/ / / ANS

2 3

setuptools easy_install upgrade to 0.6c8 problem
by Scott Brown 28 Apr '08

28 Apr '08

I have upgraded setuptools from http://peak.telecommunity.com/DevCenter/EasyInstall to 0.6c8, but my system keep trying to use the older version 0.6c7. If I remove the older version, then I get the error message: File "/Library/Python/2.5/site-packages/setuptools-0.6c8-py2.5.egg/pkg_resources.py", line 524, in resolve pkg_resources.DistributionNotFound: setuptools==0.6c7 when I try to run easy install. When I check the installation of the new version it says that it has already been installed: sudo python ez_setup.py Setuptools version 0.6c8 or greater has been installed. (Run "ez_setup.py -U setuptools" to reinstall or upgrade.) I am using Mac OS X 10.5. How do I completely remove all traces of the old version of setuptools and get the new version 0.6c8 recognised? Get the name you always wanted with the new y7mail email address. www.yahoo7.com.au/y7mail

2 2

Ignore ~/.pydistutils.cfg ?
by Peter Fein 26 Apr '08

26 Apr '08

is there a way to tell distutils/setuptools to ignore ~/.pydistutils.cfg? I use a config to keep easy_install'd packages in my home directory but doing so confuses MacPorts; they're apparently passing --exec/-- exec-prefix, but it seems to be getting overriden by my config. See: http://trac.macports.org/projects/macports/ticket/9831#comment :4

3 2

[ANN] stdeb 0.2
by Andrew Straw 26 Apr '08

26 Apr '08

I would like to announce the release of stdeb 0.2. = What is it? = stdeb http://stdeb.python-hosting.com/ ("setuptools debian") produces Debian source packages from Python packages via a new distutils command, sdist_dsc, which produces a Debian source package of a Python package. Automatic defaults are provided for the Debian package, but many aspects of the resulting package can be customized via a configuration file. = What's new? = This is a primarily a bug-fix release cleaning up after the alpha series which introduced many new features. Here is the detailed changelog since the last alpha release. 008-03-27 Add ability to pass environment variables to setup.py script. 2008-03-18 Do not allow '.' in source package names. 2008-01-20 Allows a user to build every dependency a package has stated on it's setup.py, recursively. 2007-10-29 Allow upstream tarball to have different name from debian .orig.tar.gz but keep md5sum. 2007-05-28 Fix bug where python distribution name contained '-' but setuptools renamed this to '_'. 2007-05-11 Fix py2dsc script to properly set __file__ and __name__. 2007-04-18 Fix bug where .egg-info renaming failed when upstream version contained '-'. = Thanks = A special thanks to Pedro Algarvio, aka s0undt3ch, for helping with this release.

2 3

PATCH: Multiple test suites
by Carlos Valiente 26 Apr '08

26 Apr '08

This patch adds support for running more than one test suite, as in: $ ./setup.py test -s foo.tests.suite,bar.tests.suite Enjoy, C

1 0

Can't generate console script with buildout - even when using zc.recipe.egg
by Anton Stonor 25 Apr '08

25 Apr '08

Hi there, I was hoping a buildout guru could give a hand on this one: The "RelStorage" package comes as an egg and installing it in a buildout environment works fine. However I can't find a way to let buildout generate the zodbconvert console script that comes with RelStorage. easy_install RelStorage adds the script fine. I know you should use zc.recipe.egg in this case, but no result. The RelStorage setup.py comes with this: scripts=['scripts/zodbconvert.py'] but no "console_scripts" entry points (maybe that is needed?) I found a kind-of workaround: entry-points = zodbconvert=zodbconvert:main extra-paths = /home/stonor/projects/mybuildout/eggs/RelStorage-1.0.1-py2.4.egg/EGG-INFO/scripts But it is annoying to hard code the path to RelStorage-1.0.1-py2.4.egg/EGG-INFO/scripts. Is there a way to dynamically look up the path to an egg with bulidout or a another way to solve my issue? /Anton Stonor

3 3

Fwd: Re: [Numpy-discussion] numpy as a setuptools dependency
by Andreas Klöckner 24 Apr '08

24 Apr '08

Ok, forwarding this to distutils-sig. :) Andreas

1 0

setuptools "install" writes to build directory
by Andreas Klöckner 24 Apr '08

24 Apr '08

Hi there, when you install a setuptools-equipped package with python setup.py build sudo python setup.py install the "install" stage writes to the build directory, as root. This is not great behavior, and will fail on NFS-mounted build roots. Can something be done to avoid this? Andreas

3 3

Providing binary packages for Python versions with different internal unicode representation
by Andreas Jung 24 Apr '08

24 Apr '08

Hi, Python interpreters can be compiled by different internal unicode representations (UCS2 vs. UCS4). Extension modules using unicode methods of Python internally can not be used with a Python interpreter with a different internal unicode representation. What's the deal when you want to provide binary packages of an extension module for Python interpreters with different unicode representations....is there some support for doing this using setuptools? Andreas

3 2

Re: [Distutils] questions on setuptools
by Phillip J. Eby 23 Apr '08

23 Apr '08

At 01:01 PM 4/23/2008 -0600, Michael Hearne wrote: >Phillip - Thanks for the quick response. One feature suggestion for >the future: > > From my perhaps naive perspective, it seems like it would be easy to >add non-PyPI dependencies that the installer could complain about. >For example, if the setup() function accepted a keyword list that >contained just the name of the package (whatever you use to import >it), and then have the installer do something like this: > >deps = ['foo','bar'] (this is the keyword list passed to the setup >function) >notfound = [] >for dep in deps: > try: > __import__(dep) > except: > notfound.append(dep) > if notfound: > print 'The following required packages are not > installed. Exiting.' >% (str(notfound)) > sys.exit(1) I don't think this is a significant enough improvement over the package aborting at runtime, to add the complexity. Plus, it removes the incentive for the depender to lobby the dependee to make their package easy_install-able. :) (And, it's actually more complex if you're trying to do version detection as well as presence detection. There's some old code in setuptools.depends that tries to do this sort of thing, but I abandoned that approach many years ago.)

1 0

questions on setuptools
by Michael Hearne 22 Apr '08

22 Apr '08

I'm creating a software package for in-house consumption, and will be using setuptools to create an egg that I can easily install, upgrade, etc. I'm able to answer most of my own questions from trolling through the documentation, but I have two that I can't find the answers for: 1) If I depend on packages that are not in PyPI and are not available through some other simple means (svn, simple .py, etc.), can I note these dependencies in such a way that easy_install will complain if they are not present and _stop_ installation? 2) If I already have a "main" script, is it possible to have that installed in /usr/local/bin (assuming my install path is "/usr/ local")? If so, how? I read this section (http://peak.telecommunity.com/DevCenter/setuptools#automatic-script-creation ) but it doesn't seem to address my issue. Thanks, Mike ------------------------------------------------------ Michael Hearne mhearne(a)usgs.gov (303) 273-8620 USGS National Earthquake Information Center 1711 Illinois St. Golden CO 80401 Senior Software Engineer Synergetics, Inc. ------------------------------------------------------

2 1

easy_install error
by Michael Hearne 22 Apr '08

22 Apr '08

I just tried to install the egg for Pyx, and got the error pasted below. I've contacted the mailing list for that project, and they seem to be unsure of where they can put shared data for their egg. The error message below says that I should contact the maintainers of the package (which I have done) and the EasyInstall maintainers for a workaround. So, is there a workaround for this? Thanks, Mike Hearne Running PyX-0.10/setup.py -q bdist_egg --dist-dir /tmp/easy_install- _D_bmc/PyX-0.10/egg-dist-tmp-r1bHsH error: Setup script exited with error: SandboxViolation: mkdir('/usr/ local/share/pyx',) {} The package setup script has attempted to modify files on your system that are not within the EasyInstall build area, and has been aborted. This package cannot be safely installed by EasyInstall, and may not support alternate installation locations even if you run its setup script by hand. Please inform the package's author and the EasyInstall maintainers to find out if a fix or workaround is available. ------------------------------------------------------ Michael Hearne mhearne(a)usgs.gov (303) 273-8620 USGS National Earthquake Information Center 1711 Illinois St. Golden CO 80401 Senior Software Engineer Synergetics, Inc. ------------------------------------------------------

2 1

Chicken and egg_info.writers problem with setup.py egg_info
by Philip Jenvey 21 Apr '08

21 Apr '08

Say you have custom egg_info.writers defined in a project's setup.py. When you use the egg_info command to restore an egg-info directory that was previously wiped out, the project's egg_info.writers aren't used. Since they aren't registered in your non-existent egg-info directory, they aren't picked up. Is it possible for the egg_info command do some boot strapping to make them work, since is has the entry_points string on hand? -- Philip Jenvey

2 1

[issue9] Emailed Bug Report re Setuptools
by Jeff Rush 21 Apr '08

21 Apr '08

New submission from Jeff Rush <jeff(a)taupro.com>: a test bug report re setuptools of the new tracker instance. ---------- messages: 14 nosy: jrush status: unread title: Emailed Bug Report re Setuptools _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue9> _______________________________________________

1 0

[issue8] A Test Issue
by Jeff Rush 21 Apr '08

21 Apr '08

New submission from Jeff Rush <jeff(a)taupro.com>: Testing a bug post. ---------- assignedto: jrush messages: 13 nosy: jrush priority: urgent status: deferred title: A Test Issue _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue8> _______________________________________________

1 0

unit testing and stub c shared libraries
by Johannes Wienke 19 Apr '08

19 Apr '08

Hi, I'm currently struggling to find a good way for running unit tests in my project. Adding a custom Command to my setup.py for running the tests wouldn't be a big problem but the unit tests need a few additional shared libraries. These libraries are simple stub files used for testing the plugin loader I'm developing. So is there a way to tell distutils to build those shared libraries only if want to run the unit tests? Otherwise those libs should be ignored because I don't want them to be installed generally. Thanks for the help Johannes

1 0

[zc.buildout] Accessing part configuration from other recipe?
by Andreas Jung 18 Apr '08

18 Apr '08

Hi, is it possible to get hold of the buildout configuration of part A from within the recipe configured for part B? Usecase: the configuration of part A should work as blueprint for actions performed through the recipe configured for part B. Andreas

2 1

Re: [Distutils] zip_safe=False not being respected? [it gets worse]
by Phillip J. Eby 18 Apr '08

18 Apr '08

At 12:02 PM 4/18/2008 -0400, Alexander Michael wrote: >On Fri, Apr 18, 2008 at 10:38 AM, Chris Withers ><chris(a)simplistix.co.uk> wrote: > > Alexander Michael wrote: > > > > > By default, setuptools enabled setup.py's install eggs (either zipped > > > or unzipped) so that you can multiple version installed (but only one > > > active, of course). If you want to install just a single version as a > > > standard python package directory, then use the > > > --single-version-externally-managed option as described in the > > > documentation: > > > > > > > $ python2.4 setup.py install --home=$INSTANCE \ > > --single-version-externally-managed > > running install > > error: You must specify --record or --root when building system packages > > > > Sadly neither the --record or --root options appear to be documented > > anywhere... > >That is sad. There is a hint from "python setup.py install --help": > --root install everything relative to this > alternate root directory > --record filename in which to record list of > installed files > >Maybe they're provided by standard distutils? I know the seuptools >documentation doesn't reiterate anything about distutils, just the >additions. Correct: --root and --record are standard distutils options. In this case, you want --record, not --root. The reason this option requires either --root or --record, is so that you have a way to know what was installed and uninstall it. In the --root case, everything installed will be under a single directory tree, and in the --record case, you'll have a list of the files.

1 0

Re: [Distutils] zip_safe=False not being respected? [it gets worse]
by Alexander Michael 18 Apr '08

18 Apr '08

On Fri, Apr 18, 2008 at 10:38 AM, Chris Withers <chris(a)simplistix.co.uk> wrote: > Alexander Michael wrote: > > > By default, setuptools enabled setup.py's install eggs (either zipped > > or unzipped) so that you can multiple version installed (but only one > > active, of course). If you want to install just a single version as a > > standard python package directory, then use the > > --single-version-externally-managed option as described in the > > documentation: > > > > $ python2.4 setup.py install --home=$INSTANCE \ > --single-version-externally-managed > running install > error: You must specify --record or --root when building system packages > > Sadly neither the --record or --root options appear to be documented > anywhere... That is sad. There is a hint from "python setup.py install --help": --root install everything relative to this alternate root directory --record filename in which to record list of installed files Maybe they're provided by standard distutils? I know the seuptools documentation doesn't reiterate anything about distutils, just the additions.

1 0

zip_safe=False not being respected?
by Chris Withers 18 Apr '08

18 Apr '08

Hi All, I'm trying to install a package into a Zope INSTANCE_HOME with: python2.4 setup.py install --home=$INSTANCE_HOME ...however, this is leaving me with an easy-install.pth and a .egg file in $INSTANCE_HOME, even though the package has zip_safe=False in its setup.py. What gives? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 6

programatically making eggs
by David Pratt 18 Apr '08

18 Apr '08

Hi. What would be the best way of programatically making eggs as opposed to python setup.py bdist_egg sdist on the command line. Many thanks.

2 3

How to test setup.py with easy_install?
by skip＠pobox.com 18 Apr '08

18 Apr '08

So I've just added install_requires=["lockfile>=0.2"] to my setup() call. How do I test that from within my local source repository? Running "python setup.py install" doesn't seem to do anything with it (I didn't expect it to). I assume I have to get easy_install to process the setup.py file in the current directory somehow, but I don't see how. Thanks, Skip

1 1

Re: [Distutils] [Python-3000] sizeof(size_t) < sizeof(long)
by David Cournapeau 17 Apr '08

17 Apr '08

Greg Ewing wrote: > When you go into a computer store and ask for > 256MB of RAM, you don't expect to be asked "What size > bytes would that be, then, sir?" > I ask for "256 Mo", Mo for Mega-octet: French (and most non English languages I am aware of) does not have this ambiguity :) And anyway, in a computer store, you find memory for personal computers, where one byte always has 8 bits. > So it's a de facto standard, and one that works perfectly > well. Going against it is both futile and unnecessary, > as far as I can see. > Going against the C standard seems pretty futile to me. cheers, David

2 1

Setuptools: problem with setuptools.command.bdist_egg:write_stub
by Ian Bicking 17 Apr '08

17 Apr '08

In setuptools.command.bdist_egg:write_stub() Setuptools writes this function out alongside .so files: def __bootstrap__(): global __bootstrap__, __loader__, __file__ import sys, pkg_resources, imp __file__ = pkg_resources.resource_filename(__name__,<resource filename>) del __bootstrap__, __loader__ imp.load_dynamic(__name__,__file__) __bootstrap__() This is problematic on App Engine, as the .py file is loaded because .so files cannot be imported. However, unlike a zip file (where I assume this function is intended to be used) there is no __loader__. As a result "del __loader__" fails. I submitted this to App Engine (http://code.google.com/p/googleappengine/issues/detail?id=229), but I also think Setuptools is creating an unnecessarily fragile function here. -- Ian Bicking : ianb(a)colorstudy.com : http://blog.ianbicking.org

2 1