-
Notifications
You must be signed in to change notification settings - Fork 24
Throttle username logins #83
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
Conversation
|
Tests fail for python3.3 - I think this project needs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you might need to move this into setUp and use reverse instead of reverse_lazy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR isn't ready for reviews yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just suggesting a solution for your test failures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm seems like it's the cause - thanks!
|
@ian-foote @meshy review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be explained with a comment/docstring, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 docstring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
|
Looks good to me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would just use status.HTTP_429_TOO_MANY_REQUESTS directly. I don't think this is any clearer and it requires looking in more places.
|
Hm... coveralls is reporting that coverage has decreased... |
|
@meshy the line it complains about if it's your concern. |
|
Test an authenticated user. If the line isn't hit then it doesn't need to be there. |
It is needed there. Will add additional test then. |
|
Can this be merged? The coverage is 100% (well, 99% for Django 1.6 .. ) |
|
Why are those lines missed on Dj1.6? |
|
Because django 1.6 doesn't support checks. |
|
|
|
👍 |
|
Thanks! |
No description provided.