[Distutils] python version information in .egg-info directory name

[Andrew Straw]

Phillip J. Eby wrote:
> At 08:42 AM 7/4/2006 +0200, Matthias Klose wrote:
>   
>> Phillip J. Eby writes:
>>     
>>>> what about installing the .egg-info directory without version
>>>> information when --single-version-externally-managed is used?
>>>>         
>>> Note that the .pyc files will be built for a specific Python version;
>>> that's why the version number is there.
>>>       
>> yes, but this shouldn't be necessary if you install into a path which
>> is known to belong to a specific python version
>> (i.e. /usr/lib/python2.4/site-pacakges)
>>     
>
> Setuptools doesn't inspect the path it's installing to in order to know 
> whether it happens to contain the Python version already.  :)  I don't see 
> what problem you're trying to solve here.
>   
The problem he's trying to solve is that the new Debian Python policy
allows a single directory tree of .py files (not the .pyc and .pyo
files) to serve all installed Python versions. The .pyc files get placed
in a separate tree which is, obviously, versioned.

I don't see what problem you're trying to solve by having the python
version number in the .egg-info/ directory name. :) Is there any
Python-version-specific info the in the .egg-info directory? How 'bout
in the case when it is installed with
--single-version-externally-managed command, which what we're talking
about with Debian, anyway?

Anyhow, this is also creating an issue for me with stdeb because I'm
trying to get the generated source packages as close as possible to
Debian policy.

Cheers!
Andrew