Skip to content

Fix the Django 1.9 compatibility with the Meta api #3511

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

Closed
wants to merge 5 commits into from

Conversation

dulacp
Copy link
Contributor

@dulacp dulacp commented Oct 16, 2015

Use backward compatible implementation for the meta api calls, as suggested in the documentation.

Cheers

@dulacp
Copy link
Contributor Author

dulacp commented Oct 16, 2015

It seems like it will fail, because I've just see that Options.get_fields has been introduced in Django 1.8.
I will fix the compatibility with previous Django versions.

@dulacp dulacp force-pushed the fix-django19-meta-api branch from 6cf54b0 to 0a89478 Compare October 16, 2015 13:38
@xordoquy
Copy link
Collaborator

I was about to update this to master and merge it but it conflicts with #3656.
Any link / explanation about get_relation_accessor_name / get_relation_field which the other PR was missing ?
Doesn't seem to break things so I'm a bit lost about the what's their goal.

@dulacp
Copy link
Contributor Author

dulacp commented Feb 27, 2016

The merged #3656 PR solved all these issues, so I'm closing mine
Cheers

@dulacp dulacp closed this Feb 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants