-
Notifications
You must be signed in to change notification settings - Fork 95
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
Drop support for Python 3.4 #512
Milestone
Comments
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
I will push this for the next release, because I found out I've done the same thing with python 3.3. It was end of life September 2017. I stopped supporting it almost a year before because of Django 1.9, on January 2017. |
dennissiemensma
added a commit
that referenced
this issue
Aug 3, 2018
Merged to |
I will allow Python 3.4 for a few more months, but I'll keep it unsupported. |
Will be released with #616. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is blocking for #510.
And Python 3.4 will be supported until early next year, so at least six months.
TODO
The text was updated successfully, but these errors were encountered: