[BangPypers] Do you pin your requirements.txt ?
Noufal Ibrahim
noufal at nibrahim.net.in
Mon Sep 16 05:00:55 CEST 2013
Kiran Jonnalagadda <jace at pobox.com> writes:
[...]
> I only have more experience with long term maintenance of code.
>
> Pinned requirements == complacency == future breakage, when maintenance is
> much more expensive than it is today.
>
> We deploy multiple times a day and I don't find that the gap between a
> Travis test and production deployment is so long that an upstream release
> within those few seconds broke compatibility.
You've obviously zeroed in a workflow that works for you. My general
experience is that pinning requirements reduces daily headaches but I
can see (and have felt) the long term bitrot problem you've talked
about. Maybe I should try doing things this way.
[...]
--
Cordially,
Noufal
http://nibrahim.net.in
More information about the BangPypers
mailing list