Closed grucha closed 4 years ago
Thank you very much for this insightful contribution. The only one thing that is missing is a failing test. Could you please add one?
Ok, will do.
o co chodzi? :)
27.01.2018 12:05 PM "grucha" notifications@github.com napisał(a):
Ok, will do.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/iplweb/django-password-policies-iplweb/pull/1#issuecomment-360980474, or mute the thread https://github.com/notifications/unsubscribe-auth/ANW39Tep_5DIWUYK95IAkI7SLqzaHlm2ks5tOxEIgaJpZM4RtgnW .
Wouldn't it be better to check from django import VERSION
than catching a TypeError
?
Patches accepted
Wysłane z iPada
Wiadomość napisana przez dnsl48 notifications@github.com w dniu 28.03.2018, o godz. 22:25:
Wouldn't it be better to check from django import VERSION than catching a TypeError?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Are you going to merge this?
Of course. As soon as I get a patch with a failing test. I think I stated this in my first comment in 2018 here https://github.com/iplweb/django-password-policies-iplweb/pull/1#issuecomment-360615064
Do you have an ETA?
No, but you can submit a pull request!
Django 1.9 is pretty old ATM and the test patch I requested never came. Closing!
From django 1.9 onwards the
permission_denied
view takes mandatory second positiopnal argument (exception
).Try going to password reset view (or any view based on
LoggedOutMixin
) while you're logged in - you'll get aTypeError
instead of a 403 response.