At 11:21 AM 11/27/2008 -0600, Brian Cameron wrote:
Is there any value in shipping these files when not delivering as Eggs, or
could they safely be just removed?
They cannot safely be removed, for several reasons, including:
1. They identify the installed package so that:
a) code which looks fo
You should probably leave them intact -- they add metadata about the
packages and allow setuptools/easy_install/pkg_resources/etc to use
those installed packages when resolving dependencies.
Nathan
On Thu, Nov 27, 2008 at 9:21 AM, Brian Cameron <[EMAIL PROTECTED]> wrote:
>
> Last October, I sent
Last October, I sent an email to this list asking how to install modules
which use setuputils so that modules are shipped in a way that is compatible
with Solaris packaging. It was recommended to me to run "setup.py install"
with the "--root=/foo" argument and this causes the files to be install
Marius Gedminas, on 2008-11-25:
> On Tue, Nov 25, 2008 at 07:34:24PM +0100, Jan Matejek wrote:
>> Is it just me, or are the messages that come in lately broken right in
>> the middle of headers? there's a stray "\n" and it appears that a part
>> of the following line is missing too. Because of that
On 27.11.2008 13:32 Uhr, Chris Withers wrote:
Andreas Jung wrote:
in buildout I can define only one alternative index server using
'index = http://pypi.zopyx.com'. Now we are in the situation where we
are running two internal index servers (one for our own internal
packages and one PyPI mirror).
Andreas Jung wrote:
in buildout I can define only one alternative index server using 'index
= http://pypi.zopyx.com'. Now we are in the situation where we are
running two internal index servers (one for our own internal packages
and one PyPI mirror). Is there some reason for this limitation? I
