2014-09-20 6:42 GMT+02:00 Russell Keith-Magee <russ...@keith-magee.com>: > > Historically, Django hasn't been deeply involved in process of developing > WSGI and related standards; this is an opportunity for us to change that > trend. >
To me the situation is pretty clear. Either this line will win: https://mail.python.org/pipermail/web-sig/2014-September/005257.html Then maybe there's a chance we'll end up with a gateway interface that doesn't make every framework undo the transformations performed by the gateway to get back to the HTTP stuff. Or that line will: https://mail.python.org/pipermail/web-sig/2014-September/005258.html. Then we'll carry the legacy of PEP 3333 and WSGI will remain the bastard child of CGI that it is and we'll keep doing stuff like value = value.encode (ISO_8859_1).decode(UTF_8) and we'll want to stab ourselves whenever we look at WSGI-related code. I'll get in touch with Graham. For the record I once started writing a PEP for a better WSGI, then I read web-sig and I carefully archived my draft without telling anyone. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mXtravDT%2BLhN0-hS9h4uewSGVXqWdEuD-oz%3DLLgSV5%2B1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
