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
Philip wrote:
When a distutils package does it. I'm not positive, but if 'pip' supports
namespace packages without using .pth files, then it has to use a shared
__init__ also.
And in the long run, easy_install will do this too.
So, the uninstallation code should simply not remove file(s)
At 01:33 PM 2/24/2009 +0100, Tarek Ziadé wrote:
Philip wrote:
So, the uninstallation code should simply not remove file(s) that
are referenced by more than one manifest in the target directory --
a relatively simple, future-proof safeguard, that doesn't require
any specific knowledge of
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
On 24 Feb, 2009, at 13:33, Tarek Ziadé wrote:
2009/2/24 Joachim König h...@online.de:
An other option could be to put the egg-info dir into the package
itself, e.g.
zlib/
__init__.py
egg-info/
PKG-INFO
MANIFEST
RECORD
...
This would require setuptools and pip to
On Tue, Feb 24, 2009 at 04:39:24PM +0100, Ronald Oussoren wrote:
On 24 Feb, 2009, at 13:33, Tarek Ziadé wrote:
2009/2/24 Joachim König h...@online.de:
An other option could be to put the egg-info dir into the package
itself, e.g.
zlib/
__init__.py
egg-info/
PKG-INFO
At 04:45 PM 2/24/2009 +0100, Ronald Oussoren wrote:
What about another interoperability hook for system packages: specify
a file that a (system) package manager can include into the egg-info
directory (or egg-file) to tell setuptools/pip that this egg is
managed by the system and hence shouldn't
At 06:21 PM 2/24/2009 +, Floris Bruynooghe wrote:
On Mon, Feb 23, 2009 at 09:53:17PM -0500, P.J. Eby wrote:
So, the uninstallation code should simply not remove file(s) that are
referenced by more than one manifest in the target directory -- a
relatively simple, future-proof safeguard,
2009/2/24 P.J. Eby p...@telecommunity.com:
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
At 02:57 PM 2/24/2009 -0500, P.J. Eby wrote:
At 04:45 PM 2/24/2009 +0100, Ronald Oussoren wrote:
What about another interoperability hook for system packages: specify
a file that a (system) package manager can include into the egg-info
directory (or egg-file) to tell setuptools/pip that this
On Feb 24, 2009, at 12:48 PM, Andrew Straw wrote:
But that is already implemented via file/dir permissions.
That's what's beautiful about GNU stow. Look:
sudo mkdir /usr/local/stow/grozz
sudo chown `whoami` /usr/local/stow/grozz
python ./setup.py install --prefix=/usr/local/stow/grozz #
11 matches
Mail list logo
