Skip to content

fixes #8, deprecation for GenericForeignKey in Django1.9 and bump version #9

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

Merged
merged 2 commits into from
Nov 19, 2015
Merged

fixes #8, deprecation for GenericForeignKey in Django1.9 and bump version #9

merged 2 commits into from
Nov 19, 2015

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.

vinit Kumar added 2 commits November 19, 2015 13:13
version

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.
tzangms added a commit that referenced this pull request Nov 19, 2015
fixes #8, deprecation for GenericForeignKey in Django1.9 and bump version
@tzangms tzangms merged commit c0c234c into StreetVoice:master Nov 19, 2015
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling ef59c4f on vinitkumar:fix/deprecation-warning into ** on StreetVoice:master**.

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.

3 participants