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.

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 django 1.11 and python 2.7 #353

Merged
merged 1 commit into from
Oct 30, 2020
Merged

Drop django 1.11 and python 2.7 #353

merged 1 commit into from
Oct 30, 2020

Conversation

jonathan-s
Copy link
Contributor

As support is deprecated for django 1.11 and python 2.7 we drop them from travis and tox. As of this pull request it works but we make no guarantees of it working going forwards.

@ZuluPro
Copy link
Contributor

ZuluPro commented Sep 26, 2020

Hi @jonathan-s
I'm not a real fan of maintaining old version,
But I think it should be a challenge of DBBackup.

I think about people with an old project,
They may want to backup before upgrading.

@jonathan-s
Copy link
Contributor Author

@ZuluPro For the next version we'll have a changelog where we can be clear that this happening. We could also minimize an accidental upgrade by making the next version 4.0.0 instead of 3.4.0

@jonathan-s
Copy link
Contributor Author

Going to merge this in as I need to use python3 and don't want to maintain compatibility with python 2 any more.

@jonathan-s jonathan-s merged commit 55cf351 into master Oct 30, 2020
@jonathan-s jonathan-s deleted the drop-1.11 branch October 30, 2020 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants