Skip to content

Dropped support for Python 3.2. #841

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 16, 2016
Merged

Dropped support for Python 3.2. #841

merged 1 commit into from
Jun 16, 2016

Conversation

timgraham
Copy link
Contributor

No description provided.

@aaugustin
Copy link
Contributor

Why should we drop support for Python 3.2 now? Django 1.8 still supports it.

@timgraham
Copy link
Contributor Author

Most third-party apps I've seen have dropped support for Python 3.2.
Django 1.8 will drop support for Python 3.2 at the end of the year.
The tests don't run for me locally due to the latest version of pip not supporting Python 3.2.
Python 3.2 is end-of-life as of this past February, although there might be one more security release this weekend based on a python-dev thread.
I think anyone still using Python 3.2 doesn't need the latest version of the toolbar.

@aaugustin
Copy link
Contributor

Fair enough.

@aaugustin aaugustin merged commit a63a0bc into django-commons:master Jun 16, 2016
@timgraham timgraham deleted the py32 branch June 16, 2016 13:07
ryneeverett pushed a commit to ryneeverett/django-debug-toolbar that referenced this pull request Oct 2, 2016
@aaugustin
Merge pull request django-commons#841 from timgraham/py32
83b8c9f 
Dropped support for Python 3.2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@timgraham @aaugustin