Skip to content

Conversation

@binarysubstrate
Copy link
Contributor

Fixes #50

@coveralls
Copy link

coveralls commented Nov 14, 2016

Coverage Status

Coverage decreased (-0.3%) to 89.691% when pulling 280aa0a on binarysubstrate:issue_50 into 6ffc60e on JBKahn:master.

4 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 89.691% when pulling 280aa0a on binarysubstrate:issue_50 into 6ffc60e on JBKahn:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 89.691% when pulling 280aa0a on binarysubstrate:issue_50 into 6ffc60e on JBKahn:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 89.691% when pulling 280aa0a on binarysubstrate:issue_50 into 6ffc60e on JBKahn:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 89.691% when pulling 280aa0a on binarysubstrate:issue_50 into 6ffc60e on JBKahn:master.

@JBKahn
Copy link
Owner

JBKahn commented Nov 14, 2016

LGTM, the error is because of the Django 1.0.3 bug as referenced in the #48 which was patched in Django 1.10.4 (unreleased)

@JBKahn JBKahn merged commit a6b82b7 into JBKahn:master Nov 14, 2016
@JBKahn
Copy link
Owner

JBKahn commented Nov 14, 2016

Thanks for the PR :)

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