--
You received this message because you are subscribed to the Google Groups "modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/fe09f599-e2bc-40df-9613-12b5ead38d58n%40googlegroups.com.
<wsgi-env-issue.zip>
Can you use the recommended daemon mode of mod_wsgi and when doing so set the lang/locale to what you use.See the lang/locale options in:
--
You received this message because you are subscribed to the Google Groups "modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/6ca07f28-b050-4e76-b6c1-040ef014c5d7n%40googlegroups.com.
[snip]
Now it wasn't practical in Python 3 to pass through variables as byte strings as the range of operations you could do on byte strings was very limited. Thus the rule for WSGI under Python 3 was that the WSGI server was required to take the underlying byte stream and convert it to the unicode capable default string as ISO-8859-1 (Latin-1). It was then up to the WSGI application to convert that to another string with the correct encoding. Since it was a unicode string at that point, to do that it would need to do.
value.encode('ISO-8859-1').decode('UTF-8')
raw_unicode_escape | Latin-1 encoding with \uXXXX and \UXXXXXXXX for other code points. Existing backslashes are not escaped in any way. It is used in the Python pickle protocol. |
--
You received this message because you are subscribed to the Google Groups "modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/c46d8d94-c59c-4dec-832a-8859a49764a0n%40googlegroups.com.