-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review supported Django Versions and Compat #3408
Comments
@tomchristie @xordoquy — If you make a decision here I'm happy to tidy up the compat module. |
Well we'll certainly want to drop 1.5 for 3.3 so I'd suggest that as a commit. |
1.6 also possible, but treat as a seperate commit if so. |
Seconded. This will allow us to drop support for Python 2.6 as well. |
I think dropping 2.6 for 3.3 should be unambiguous as well, right? |
We'll make it clear but once Django 1.5 / 1.6 will be removed from the supported version we won't have any Django compatible with Python 2.6. |
So drop 1.6? |
I think we should drop python 2.6. |
OK, I'll make the PR assuming dropping both — we can always change our minds before merging. (Anyone on Django 1.6 could use v3.2.x — which would still work for them — they can't be that bothered about what versions they're on anyhow...) |
py1.7+ dj1.6+ would seem reasonable to me at this point, but deps on how much of compat we can remove if we also drop dj1.6 |
I'd rather we align the supported Python version to what Django does but won't oppose it. |
I agree here. If we keep Django 1.6, we should keep Python 2.6. (Opinion) I'll do it in stages, keeping 2.6/1.6 to begin. Then I'll have a look at what we can drop if we get rid of it and we can decide then. |
Let me know if / how I can help here. |
OK. Will do! 👍 |
Got some time this evening, will do. |
I'm going to close this. Whatever we decide on #3429 settles it. |
Following the discussion in #3405
compat.py
in accordance with that.The text was updated successfully, but these errors were encountered: