Hi!
I think you've found the wrong mailing list for this post. This mailing
list is for discussing the development of Django itself, not for support
using Django. This means the discussions of bugs and features in Django
itself, rather than in your code using it. People on this list are unlikely
Request Method: GET
Request URL: http://localhost:8000/
Django Version: 3.0.7
Exception Type: AttributeError
Exception Value:
module 'json' has no attribute 'JSONDecoder'
Exception Location:
E:\Blogs\ll_env\lib\site-packages\django\contrib\messages\storage\cookie.py
in , line 27
Python
Alexander, it's not really up for debate any more. We've already merged the
PR's to Django.
On Sat, 20 Jun 2020 at 13:51, Alexander Lyabah wrote:
> let's not change the subject
>
> we are not talking about black and white, we are talking about whitelist /
> blacklist and master / slave. Those
let's not change the subject
we are not talking about black and white, we are talking about whitelist /
blacklist and master / slave. Those statements have a big history in
programming, which has nothing to do with slavery at all.
Don't mix words with meaning and senses.
... It is important
Ahmad,
> we should strive to set an international standard
No, we shouldn't we are here for creating framework, just treat your child
well and it is enough to changing the world for the best.
> If a certain word is off-putting or problematic to individuals in our
community
We can always
Thanks to Paul for this proposal, and for working to put proper timezone
usage into Python itself. PEP 495 and 615 definitely make Python better,
and it seems inevitable that everyone will sooner or later switch over. I'm
all for getting this process going in Django.
I have doubts over whether
