This won't auto update when something comes out though. If I'm the prod
server and I'm on 1.3.2, and then someone asks me to pip update to django
<= 1.4, I'm going to think "Great i'm already on django <= 1.4". I agree
with Cory that it's good to know what version we're on.


On Tue, Aug 6, 2013 at 2:54 PM, dmyung <notifications@github.com> wrote:

> In requirements/requirements.txt:
>
> > @@ -5,7 +5,7 @@ restkit==4.2.0
> >  couchdbkit==0.5.7
> >  celery==3.0.15
> >  decorator==3.3.2
> > -django==1.3.1
> > +django <= 1.4
>
> I thought of that, but the point of the 1.3.x releases is that they're
> security fixes that should be trivially upgraded to. By being on a fixed
> point release we don't necessarily have timely updates.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dimagi/commcare-hq/pull/875/files#r5613022>
> .
>