-----BEGIN PGP SIGNED MESSAGE-----
Chris Withers wrote:
> Tres Seaver wrote:
>> Chris Withers wrote:
>>> Tres Seaver wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> I mean an index which supplies the 'simple' PyPI interface, such that we
>>>> could tell people to 'easy_install' from it, e.g.:
>>>> $ /path/to/bin/easy_install -i http://kgs.zope.org/Zope2/2.1.2
>>> But how do you then set things up when you want to use other eggs that
>>> are only available on PyPI? Surely as soon as you add PyPI as an egg
>>> source, things go belly up?
>> Personally, I evaluate such eggs in a sandbox, and then add them to the
>> project-specific index once I'm sure that they work with the other
>> software in the index: I don't use PyPI at all when building out
>> production sites.
> That seems overly heavyweight for the average new user.
> "no, sorry, you can't use Zope 2.12 with anything other than what it
> comes with unless you get your own egg repository running"
Who is talking about an "average new user"? I'm talking about the "my
revenue stream depends on this application working" professional (me),
and the best practices I use. PyPI is *great* as a tool for discovering
new stuff: it sucks as the basis for a repeatable build environment.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -