Re: [Distutils] Utility to mirror an egg index from a Debian distribution

On Sat, May 16, 2009 at 07:13:43AM -0400, David Lyon wrote: Hi Brian, Hi David, It sounds interesting. I might be interested in helping. Great :) What I would like to do is make a test script to download all the packages off pypi and build them under multiple platforms. Basically,

[Distutils] Version string normalization

Hello, I've just noticed that when using setuptools, the name of the file created by the sdist command changes. The version passed to setup is 0.9.33+r17283 but the file written is Nevow-0.9.33-r17283.tar.gz. This change causes various problems for me. How can I avoid it? Thanks, Jean-Paul

Re: [Distutils] Version string normalization

At 04:00 PM 5/18/2009 -0400, Jean-Paul Calderone wrote: Hello, I've just noticed that when using setuptools, the name of the file created by the sdist command changes. The version passed to setup is 0.9.33+r17283 but the file written is Nevow-0.9.33-r17283.tar.gz. This change causes various

[Distutils] setup tools maximum recursion depth exceeded

There's been a previous post (Tarek, Fixing the mess in sdist/egg_info) about the fact that setuptools fails due to a circular dependency: distutils.sdist.run() - setuptools.build_py.data_files - setuptools.egg_info.run() - distutils.sdist.add_defaults() - setuptools.build_py.data_files - etc

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

Hi all, I've just had a moment to read PEP-376.. I seriously question the need for a new .EGG_INFO directory... Given that a typical site-packages directory doesn't have many files in it anyway. Typically, it will contain 20+ project/package subdirectories or .EGG files/directories. Why not

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

At 08:34 PM 5/18/2009 -0400, David Lyon wrote: Why not keep the .EGG_INFO files in the site-packages directory? That's where they go. Each installed project has its own .egg-info subdirectory containing the listed files. See the EggFormats documentation for details. PEP 376 is just adding

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

On Mon, 18 May 2009 20:59:22 -0400, P.J. Eby p...@telecommunity.com wrote: At 08:34 PM 5/18/2009 -0400, David Lyon wrote: Why not keep the .EGG_INFO files in the site-packages directory? That's where they go. Each installed project has its own .egg-info subdirectory containing the listed

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

On Tue, May 19, 2009 at 12:59 PM, P.J. Eby p...@telecommunity.com wrote: At 08:34 PM 5/18/2009 -0400, David Lyon wrote: Why not keep the .EGG_INFO files in the site-packages directory? That's where they go. Each installed project has its own .egg-info subdirectory containing the listed

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

David Lyon wrote: I seriously question the need for a new .EGG_INFO directory... Given that a typical site-packages directory doesn't have many files in it anyway. Typically, it will contain 20+ project/package subdirectories or .EGG files/directories. ;-) Mine has 213

Re: [Distutils] PEP 376 - critique - why more sub-directories within python aren't needed...

On Mon, 18 May 2009 21:22:38 -0500, Jeff Rush j...@taupro.com wrote: ;-) Mine has 213 files/directories, and I use virtualenv and buildout to keep the number down. Ok.. that sounds like it is in the normal range How many subdirectories in site-packages is not so important if they are