At 06:49 PM 7/3/2006 +0200, Matthias Klose wrote:
At 10:28 PM 6/9/2006 +0200, Matthias Klose wrote:
Phillip J. Eby writes:
At 09:51 PM 6/9/2006 +0200, Matthias Klose wrote:
Hi,
when installing an egg in a system-installed python version, then you do have another python version information in the egg_info directory name (py2.x). Is it possible or advisable to exclude that information from the name? At least I know that I'm installing into /usr/lib/python2.3/site-packages.
I don't understand your question. There is no 'egg_info'
you talking about a .egg/EGG-INFO directory or an '.egg-info'
Phillip J. Eby writes: directory. Are directory?
sorry,
/usr/lib/python2.3/site-packages/setuptools-0.6b2-py2.3.egg-info
would it be safe to rename that to
/usr/lib/python2.3/site-packages/setuptools-0.6b2.egg-info
without loosing functionality?
Yes.
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. Not including the version number won't magically make it work with other Python versions.
Another unrelated thing: Debian is supposed to ship the source code for binaries, but it's not included in the package for cli.exe and gui.exe. Could you point me to the source code and/or include it in the next release?
It's included in the source release, along with all the documentation. The file you're looking for is 'launcher.c'. Of course, the .exe files aren't used on non-Windows platforms anyway.