The travis run on #278 failed because Travis was testing us against
Django 1.7 and Python 2.6, which isn't supported. I realized our
version specifiers weren't consistent with eachother and decided to
fix them up.
Now all of the specifiers act like the ~= operator from PEP 440 and
install the latest compatible version within each major Django version
while testing, which I think better mirrors the versions our users
are going to be using.
This PR is mostly so I can see if Travis likes the changes. :D
Osmose
commented
9 years ago
The travis run on #278 failed because Travis was testing us against Django 1.7 and Python 2.6, which isn't supported. I realized our version specifiers weren't consistent with eachother and decided to fix them up.
Now all of the specifiers act like the
~=operator from PEP 440 and install the latest compatible version within each major Django version while testing, which I think better mirrors the versions our users are going to be using.This PR is mostly so I can see if Travis likes the changes. :D