[BangPypers] Do you pin your requirements.txt ?

[Kiran Jonnalagadda]

We almost never pin at HasGeek. If an external library breaks API, we
upgrade our code ASAP (we discover breakage from Travis reports).

Between the risk of breaking code and having the hot seat at any hint of
bit rot, I find the latter preferable.

Kiran

-- 
Kiran Jonnalagadda
http://jace.zaiki.in/
http://hasgeek.com/

(Sent from my phone)
On Sep 14, 2013 10:50 PM, "Noufal Ibrahim" <noufal at nibrahim.net.in> wrote:

> Dhananjay Nene <dhananjay.nene at gmail.com> writes:
>
>
> [...]
>
> > The difficulty with that approach (I've never actually done it) is
> > that it requires versioning these bundles, make them available to your
> > installation scripts and code to them (lately I've started using
> > ansible to do this).
>
> I know. I don't think I'd do it again. This was a stop gap thing back
> then.
>
>
> [...]
>
> > After realising distributions eventually disappear pypi (central),
> > makes sense to have your own pypi mirror which lacks the feature of
> > disappearing dists.
>
> I actually had a script which would make a bundle and then wrap it up in
> a self extracting script (using makeself). If you ran it, it would serve
> the packages in that bundle as a local PyPI mirror which you could
> install off of.
> [...]
>
>
> --
> Cordially,
> Noufal
> http://nibrahim.net.in
> _______________________________________________
> BangPypers mailing list
> BangPypers at python.org
> https://mail.python.org/mailman/listinfo/bangpypers
>