Skip to content

Get rid of Django 2.0 DeprecationWarning #78

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 3 commits into from
May 10, 2017

Conversation

coagulant
Copy link
Contributor

@coagulant coagulant commented Mar 26, 2017

Get rid of Django 2.0 DeprecationWarning and add 1.11 tox env.
It also fixes faker dependency addressed in #76

@crccheck
Copy link
Owner

Thanks, I can't think right now, but feel free to bump this at any time in the future if I forget. I wish there was a github remindme bot.

@coveralls
Copy link

coveralls commented Mar 27, 2017

Coverage Status

Coverage decreased (-1.9%) to 98.113% when pulling 3339898 on coagulant:feature/django111 into 8780870 on crccheck:master.

@crccheck
Copy link
Owner

thanks, just going to merge and if there's a problem i'll fix it later. thanks for your patience

@crccheck crccheck merged commit d3fb875 into crccheck:master May 10, 2017
@crccheck crccheck mentioned this pull request May 10, 2017
@coveralls
Copy link

coveralls commented May 10, 2017

Coverage Status

Coverage decreased (-100.0%) to 0.0% when pulling fa9ce4c on coagulant:feature/django111 into 011ed07 on crccheck:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-100.0%) to 0.0% when pulling fa9ce4c on coagulant:feature/django111 into 011ed07 on crccheck:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 0.0% when pulling fa9ce4c on coagulant:feature/django111 into 011ed07 on crccheck: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