Thanks for the well-reasoned response Nick.
Donald: +1 to your proposal. This will increase stability for the main
package repository, which is a good direction to move toward.
On Sun, Sep 28, 2014 at 3:51 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 29 Sep 2014 07:37, M.-A. Lemburg
Another option (along the lines of conda) is pex, which zips up you code +
dependencies into a single, zipped executable.
https://github.com/pantsbuild/pex
Pex has been relatively nice for us, as we can bundle our applications into
(mainly) hermetically-sealed binaries, which works well on
require
any sort of runtime logic.
On Aug 28, 2014, at 6:39 PM, Joe Smith yasumo...@gmail.com wrote:
Naive question- does pip send over a UserAgent (or something) that
contains a version number the server can use to determine which behavior to
default to?
That would allow a deprecation cycle
Naive question- does pip send over a UserAgent (or something) that contains
a version number the server can use to determine which behavior to default
to?
That would allow a deprecation cycle of N months or so that will let people
upgrade from 1.5 to 1.6. We could then watch usage of 1.5 decrease
