Tarek Ziadé wrote:
So basically site-packages is a distribution location that is
avoided by everyone because it doesn't
know how to handle multiple versions.
I think you overrate the importance of having multiple versions of a
package available
for the same python interpreter. If you have m
Tarek Ziadé wrote:
ok so far, from the whole dicussion it seems that everyone agrees that
the Python version is superfluous
in the .egg-info files, so I'll update the PEP for this point.
I'll also start to write more details about uninstallation
As P.J.Eby pointed out the importance of PEP
Tarek Ziadé wrote:
If you look at install_egg_info, it will add the Python version
http://svn.python.org/projects/python/trunk/Lib/distutils/command/install_egg_info.py
I am not sure either this should be kept. I don't see the rationale
either, since
sys.version is known at runtime, it seems
P.J. Eby schrieb:
At 09:39 AM 2/24/2009 +0100, Joachim König wrote:
could the egg-info directory be put somewhere else (as a
configuration/command line option)?
No, since it's used to identify the installed location of the code
that goes with it, ala PEP 262. In other words, sys.path is its
Phillip J. Eby wrote:
It would be, if .eggs were a packaging format, rather than a binary
distribution/runtime format.
Remember eggs are to Python as jars are to Java -- a Java .jar
doesn't contain documentation either, unless it's needed at
runtime. Same for configuration files.
But
Phillip J. Eby wrote:
Second, there were no uninstall tools for it, so I'd have had to
write one myself. (Zed's easy_f'ing_uninstall to the contrary, it
ain't easy, and I have an aversion to deleting stuff on people's
systems without knowing what will break. There's a big difference
