Mailman 3 January 2008 - Distutils-SIG

Re: [Distutils] setuptools, bdist_wininst and dependecies
by Phillip J. Eby 14 Jan '08

14 Jan '08

At 11:05 AM 1/13/2008 +0200, Ionel Maries Cristian wrote: >I'm using setuptools for my setup script. > >when installing a .exe package dependencies aren't fetched. >should it work this way? >are there any ways getting the dependencies downloaded and still >have a bdist_wininst package ? You could put something in the post-install script to run easy_install, I suppose. :)

2 1

Egg depency order
by Iwan Vosloo 14 Jan '08

14 Jan '08

Hi there, I need to get a list of eggs in 'dependency' order: a list with eggs (Distribution objects?) which is sorted so that earlier entries will never depend on entries later in the list. [1] I spotted the _dep_map attribute on Distribution objects and it seems to have something like that already. Exactly what is in _dep_map? Could I use it to compute what I need? - Iwan [1] In fact, this is an intermediary result - I want to compute all the entry points of a tree of dependencies in such a way that the entry points of eggs deeper in the tree will always be earlier in the list than entry points for those shallower in the tree.

2 1

Finding my data_files
by Paul Moore 14 Jan '08

14 Jan '08

If I have a module which installs some files using the data_files=[...] argument to setup.py, how do I then (reliably) find those files from my code? The first question is, is there a way of obtaining the distutils data_files parameter value at runtime? If not, I guess I have to code the same information in my code as is in the setup.py script. Not ideal, but OK... The second question is, if my files are installed using a relative path, then the documentation says (section 2.7) "If directory is a relative path, it is interpreted relative to the installation prefix (Python's sys.prefix for pure-Python packages, sys.exec_prefix for packages that contain extension modules)." That's OK, but again it sounds like I need to code knowledge of whether the setup includes extension modules or not, into my code. OK, if I must, then I must, but I'd rather not do so and find out I missed something obvious... One final question, is it possible (barring obvious hacks like checking if sys.prefix or sys.exec_prefix is a prefix of module.__file__) to determine if I'm running from an installed or a development copy of my module? I have a horrible feeling that the answer to most of this will be "use setuptools", but I don't have that option, as this is not my code (it's MoinMoin, for what it's worth). Thanks, Paul.

1 0

Re: [Distutils] pypi and easy_install
by Phillip J. Eby 13 Jan '08

13 Jan '08

At 02:26 PM 12/20/2007 +0100, Giampaolo Rodola' wrote: >Oh, I'm sorry, >yestarday night it was very late (5:00 AM) and I completely >misunderstood what you said. >Thanks for your help, I'm going to rename the tarball. It will be better for you in general if you just use "setup.py sdist" to generate your tarballs, as they will then have the right name, and also will include the distutils PKG-INFO. (This is a distutils feature and doesn't require setuptools, although the distutils are a bit trickier to get the tarball to include everything, as you have to explicitly list in MANIFEST.in anything that distutils doesn't automatically pick up. Setuptools on the other hand will automatically include anything that's under revision control in your project, unless you use MANIFEST.in to tell it *not* to. CVS+SVN support is built in, plugins for various other revision control systems can be found on PyPI.)

2 1

setuptools, bdist_wininst and dependecies
by Ionel Maries Cristian 13 Jan '08

13 Jan '08

I'm using setuptools for my setup script. when installing a .exe package dependencies aren't fetched. should it work this way? are there any ways getting the dependencies downloaded and still have a bdist_wininst package ? -- ionel.

1 0

Re: [Distutils] zc.buildout and PYTHON_EGG_CACHE
by Phillip J. Eby 11 Jan '08

11 Jan '08

At 01:08 PM 1/12/2008 +1300, Michael Dunstan wrote: >On Jan 12, 2008 1:04 PM, Jim Fulton <jim(a)zope.com> wrote: > > > > On Jan 11, 2008, at 6:58 PM, Michael Dunstan wrote: > > > > > How about something in the buildout section? So that could look like: > > > > > > [buildout] > > > python-egg-cache = /some/where/here/or/there > > > > > > OK, what happens if this option isn't present? > >I'm not too sure. My first reaction is just business as usual - leave >that untouched and PYTHON_EGG_CACHE will default to ~/.python-eggs Or more precisely, the cache directory will default to PYTHON_EGG_CACHE, if it isn't explicitly set via the API.

1 0

zc.buildout and PYTHON_EGG_CACHE
by Michael Dunstan 11 Jan '08

11 Jan '08

Is there a sane way to configure a common PYTHON_EGG_CACHE using zc.buildout? By default PYTHON_EGG_CACHE is a path relative to the current users home directory which can be a permissions hassle if the built-out processes run as a restricted user. There are some details on how to configure PYTHON_EGG_CACHE outside of buildout: http://mail.python.org/pipermail/distutils-sig/2006-November/006909.html And an example egg that ends up being extracted to PYTHON_EGG_CACHE is simplejson. -- Michael Dunstan

3 5

Re: [Distutils] Passing compiler options via the pydistutils.cfg file
by Phillip J. Eby 10 Jan '08

10 Jan '08

At 10:02 AM 1/10/2008 -0800, kieran hervold wrote: >I've run into a problem using mod_python under OS X Leopard: because >the apache2 process runs in 64-bit mode, the python interpreter is >forced into 64-bit mode, which breaks compatibility with any Python >library with underlying C code. > >I suspect that adding a compiler flag specifying "-arch x86_64" to any >gcc invocation would fix the problem, but I'd rather not do this >package by package: I'd like to set one global parameter and be done >with it. > >Apparently, I can add an entry to the global pydistutils.cfg file. >However, I can't seem to find the appropriate parameter. The >pydistutils.cfg file follows the nomenclature of command-line setup.py >invocation, but I haven't found a C compiler pass-through parameter >for setup.py. > >Does such a parameter exist? Apparently not: $ python setup.py build_ext --help ... Options for 'build_ext' command: --build-lib (-b) directory for compiled extension modules --build-temp (-t) directory for temporary files (build by-products) --inplace (-i) ignore build-lib and put compiled extensions into the source directory alongside your pure Python modules --include-dirs (-I) list of directories to search for header files (separated by ';') --define (-D) C preprocessor macros to define --undef (-U) C preprocessor macros to undefine --libraries (-l) external C libraries to link with --library-dirs (-L) directories to search for external C libraries (separated by ';') --rpath (-R) directories to search for shared C libraries at runtime --link-objects (-O) extra explicit link objects to include in the link --debug (-g) compile/link with debugging information --force (-f) forcibly build everything (ignore file timestamps) --compiler (-c) specify the compiler type --swig-cpp make SWIG create C++ files (default is C) --swig-opts list of SWIG command line options --swig path to the SWIG executable --help-compiler list available compilers > If I want to add a flag ("-arch x86_64", >in this case) to the C compiler invocation, how do I pass that to >setup.py? There's probably an environment variable you can use, like CFLAGS or some such; check the distutils.sysconfig module to see if you can find something useful. Otherwise, you may have to have apache run your setup.py files to do the building.

1 0

Passing compiler options via the pydistutils.cfg file
by kieran hervold 10 Jan '08

10 Jan '08

I've run into a problem using mod_python under OS X Leopard: because the apache2 process runs in 64-bit mode, the python interpreter is forced into 64-bit mode, which breaks compatibility with any Python library with underlying C code. I suspect that adding a compiler flag specifying "-arch x86_64" to any gcc invocation would fix the problem, but I'd rather not do this package by package: I'd like to set one global parameter and be done with it. Apparently, I can add an entry to the global pydistutils.cfg file. However, I can't seem to find the appropriate parameter. The pydistutils.cfg file follows the nomenclature of command-line setup.py invocation, but I haven't found a C compiler pass-through parameter for setup.py. Does such a parameter exist? If I want to add a flag ("-arch x86_64", in this case) to the C compiler invocation, how do I pass that to setup.py? Thanks for any help, kieran hervold

1 0

reStructuredText whitespace lost when writing pkg-info
by stephen emslie 10 Jan '08

10 Jan '08

I've noticed that setuptools seems to flatten any indentation in fields when generating the PKG-INFO metadata file. I noticed this because PEP345 [1] suggests that the long description field can be written in reStructuredText (which would be excellent for my current project), but unfortunately whitespace is being lost that breaks things like literal blocks that require indentation. The trouble seems to be that distutils.util.rfc822_escape strips all excess whitespace and adds 8 spaces of padding to the start of every line. For example: >>> rest = """ ... a literal python block:: ... >>> import this ... """ >>> print distutils.util.rfc822_escape(rest) a literal python block:: >>> import this which generates a few warnings and no literal block when docutils tried to render it. Can anyone tell me if this behaviour is necessary to be rfc822/MIME compliant, or is distutils being over-cautious in flattening out all whitespace? The w3c discussion on multiple lines in rfc822 [2] seems to suggest that whitespace can be 'unfolded' safely, so it seems a shame to be throwing it away when it can have important meaning. [1] http://python.cofman.dk/peps/pep-0345.html [2] http://www.w3.org/Protocols/rfc822/3_Lexical.html Stephen Emslie

1 0

Distutils-SIG January 2008