Skip to content
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

Use six.moves to deal with urllib.urlencode and range compatibility changes #117

Open
chrisjrn opened this issue May 26, 2017 · 1 comment
Open

Use six.moves to deal with urllib.urlencode and range compatibility changes #117

chrisjrn opened this issue May 26, 2017 · 1 comment

Comments

@chrisjrn
Copy link
Owner

No description provided.

@chrisjrn chrisjrn mentioned this issue May 26, 2017
Closed
@jamezpolley
Copy link

Django 1.11 and 2.0 both support py3; so I'd suggest just switching to py3-only.

Maybe that's just because I don't realise how common django 1.8 is.. but it's been out of mainstream support for >2 years and is due to exit extended support in april 2018 thereabouts, so it doesn't seem like it's worth continuing to support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jamezpolley @chrisjrn