Drop support for Django 1.5 / 1.6 and Python 2.6 #170
Conversation
|
My opinion is that we should release ASAP as I know about several people waiting for a release with recent fixes. |
|
That's ok by me. Any idea when the next release is coming? |
|
As soon as one of the releasers finds time to do it. Sorry, I cannot be more precise. |
|
No problem, this answers my question actually. I wasn't sure if you meant ASAP to mean in the next couple of days. Thanks. |
|
Would be nice if we could move on with this... |
benkonrath
force-pushed
the
drop-support-for-django-15-16-python-26
branch
2 times, most recently
from
7749768 to
5e723f4
Compare
benkonrath
force-pushed
the
drop-support-for-django-15-16-python-26
branch
from
5e723f4 to
ae84b0a
Compare
|
I've just updated / rebased this PR. I'm just looking for a quick sanity check. Thanks. |
| @@ -1,5 +1,4 @@ | |||
| invoke==0.11.1 | |||
| coverage==3.7.1 | |||
| flake8==2.2.5 | |||
| django-discover-runner==1.0 | |||
| six==1.8.0 | |||
There was a problem hiding this comment.
Maybe six>1.8.0 (or six==1.10.0)?
There was a problem hiding this comment.
But it doesn't need to be in that PR, in fact.
|
I included the updated six version in this PR. Thanks. |
|
Looks good, please push it! |
Motivated by the unknown Django 1.5 test errors in #152, I propose we drop support for unsupported versions of Django (1.5 and 1.6) which means we can also drop Python 2.6 support. This would be for the next release of localflavor (1.2). I'm curious to hear what people think about this.