On Tue, 2020-10-06 at 23:26 -0700, James Bennett wrote:
> > Passwords obtained from previous breach corpuses.
There even appears to be a 3rd party validator for this.
Although it only checks for inclusion, not total number
breaches that password was included in, which might be
a useful indicator
On Tue, Oct 6, 2020 at 9:07 AM Florian Apolloner wrote:
> So, I have been digging a little bit more and it seems there was a conscious
> decision to not include an entropy check or character classes:
> https://groups.google.com/g/django-developers/c/9GBhgGXmEKs/m/toKKgGhaqewJ --
> But I have
Hi,
I have own login site to authenticate user, it will redirect to admin site
if these users is supper user. I try to use HttpResponseRedirect func but
it don't send POST request and POST method to login func to render Django
Administrator page. Can you help me please.
Thanks and Best
Hi Carlton,
Thanks for coming back to this.
Your reasoning makes a lot of sense. I too think it'll be good not to land
this in 3.2 LTS and focus on making any changes in 4.0.
The question is then which path we choose to take:
1. The deprecation route using pytz_deprecation_shim in 4.0
This sounds like a reasonable timeline to me. I think the breakage will
be relatively small because I suspect many end-users don't really even
know to use `normalize` in the first place, and when introducing the
shim into a fundamental library at work I did not get a huge number of
breakages, but
Hi Paul.
Thanks for the input here, and for your patience
> I am fairly certain this is going to be a tricky migration and will
inevitably come with *some* user pain. I don't think this will be Python 2
→ 3 style pain, but some users who have been doing the "right thing" with
pytz will need
I think either jumping straight to zoneinfo in 5.0 or using the shim in
4.0 would be fine, though I will say that it is very likely that if you
don't want to change your code twice you won't have to, particularly if
we add a feature flag to opt-in to zoneinfo even in 3.2.
The shim time zones
