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

Django 2.0 support #298

Merged
merged 4 commits into from Dec 11, 2017
Merged

Django 2.0 support #298

merged 4 commits into from Dec 11, 2017

Conversation

tony
Copy link
Member

@tony tony commented Dec 7, 2017

See #297 (comment)

This covers a few areas

  • Updating tox to test django 2.0
  • Upgrading travis for django 2.0
  • Use _chain in django 2.0 query chaining instead of _clone
  • Remove use_for_related_fields = True in favor of the new MRO for managers

Fixes #297

@tony
Copy link
Member Author

@tony tony commented Dec 7, 2017

Using this in production @ https://devel.tech/

@tony tony force-pushed the django-2.0 branch 7 times, most recently from 69fc69d to f40d300 Compare Dec 7, 2017
Passes in python version via travis python: param
@tony tony merged commit 749aa09 into jazzband:master Dec 11, 2017
1 check passed
@tony
Copy link
Member Author

@tony tony commented Dec 11, 2017

I'm going to go ahead and merge this into master. I'm using this in production ATM. I just had an issue on django-robots where someone overlapped with a PR for 2.0 compatibility. 😄

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.

None yet

1 participant