Skip to content

Upgrade Django #21

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
j4mie merged 3 commits into from
Apr 26, 2017
Merged

Upgrade Django #21

j4mie merged 3 commits into from
Apr 26, 2017

Conversation

@maximilianhurl
Copy link
Contributor

@maximilianhurl maximilianhurl commented Apr 25, 2017 •
edited
Loading

  • Fixes for Django 1.9+
  • Removed support for Django 1.7
  • Test against python 3.6

RealOrangeOne
RealOrangeOne reviewed Apr 25, 2017
View reviewed changes
.travis.yml
env:
- DJANGO_VERSION=1.7
- DJANGO_VERSION=1.8
- DJANGO_VERSION=1.9
Copy link
Contributor

@RealOrangeOne RealOrangeOne Apr 25, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to maintain support for EoL versions? 1.8 and 1.10 may be worthwhile as they're still supported for the next year, but 1.7 and 1.9 are both unsupported and considered insecure.

@j4mie j4mie merged commit 0b8472f into master Apr 26, 2017
@j4mie j4mie deleted the upgrade-django-versions branch April 26, 2017 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

2 more reviewers

@RealOrangeOne RealOrangeOne RealOrangeOne left review comments

@manosim manosim manosim approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@maximilianhurl @manosim @RealOrangeOne @j4mie