On Sun, 10 May 2009 09:41:33 -0600, Zooko Wilcox-O'Hearn
wrote:
>> (Of course, this ignores the issue of uninstalling previous
>> versions, or overwriting of conflicting files in the target -- does
>> pip handle these?)
>
> GNU stow does handle these issues.
I'm not sure GNU stow will handle th
Michael Foord wrote:
Nick Coghlan wrote:
Benjamin Peterson wrote:
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've k
Nick Coghlan wrote:
Benjamin Peterson wrote:
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've know hit __enter__ and
Benjamin Peterson wrote:
> A while ago, Guido declared that all special method lookups on
> new-style classes bypass __getattr__ and __getattribute__. This almost
> completely consistent now, and I've been working on patching up a few
> incorrect cases. I've know hit __enter__ and __exit__. The com
At 12:04 PM 5/10/2009 -0600, Zooko Wilcox-O'Hearn wrote:
The thing that prevents this from working with setuptools is that
setuptools creates a file named easy_install.pth during the "python
./ setup.py install --prefix=foo" if you build two different Python
packages this way, they will each cr
following-up to my own post to mention one very important reason why
anyone cares:
On Sun, May 10, 2009 at 12:04 PM, Zooko Wilcox-O'Hearn wrote:
> It is a beautiful, elegant hack because it is sooo dumb. It is also very
> nice to use the same tool to manage packages written in any programming
>
Zooko Wilcox-O'Hearn wrote:
> On May 10, 2009, at 11:18 AM, Martin v. Löwis wrote:
>
>> If GNU stow solves all your problems, why do you want to use
>> easy_install in the first place?
>
> That's a good question. The answer is that there are two separate jobs:
> building executables and putting
On May 10, 2009, at 11:18 AM, Martin v. Löwis wrote:
If GNU stow solves all your problems, why do you want to use
easy_install in the first place?
That's a good question. The answer is that there are two separate
jobs: building executables and putting them in a directory structure
of the
> GNU stow does handle these issues.
If GNU stow solves all your problems, why do you want to
use easy_install in the first place?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsub
On May 9, 2009, at 9:39 AM, P.J. Eby wrote:
It would be really straightforward, though, for someone to
implement an easy_install variant that does this. Just invoke
"easy_install -Zmaxd /some/tmpdir packagelist" to get a full set of
unpacked .egg directories in /some/tmpdir, and then move
10 matches
Mail list logo
