Skip to content

Conversation

@vinitkumar
Copy link

This commit introduces a backward compatible import where the warning is
removed for django1.8 and ensure that the project will run on Django1.9
when the support for GenericForeignKey will be removed from the generic
module in contenttype.

Please add this fix. This fix has already been merged to the master repo. StreetVoice#9. We use your work on production and require these changes to be merged so that it works on Django1.9 and above.

This commit introduces a backward compatible import where the warning is
removed for django1.8 and ensure that the project will run on Django1.9
when the support for GenericForeignKey will be removed from the generic
module in contenttype.
@hwkns
Copy link
Owner

hwkns commented Jan 3, 2016

@vinitkumar thanks! I've merged in the changes from upstream (the StreetVoice repo). Closing this PR, but let me know if there's anything more I can do.

@hwkns hwkns closed this Jan 3, 2016
@vinitkumar
Copy link
Author

@hwkns Thanks for merging the changes. 👍

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