Jens Vagelpohl
Jens Vagelpohl
Well, I was asking myself the same question if this can be closed. But even if you point someone to the different documentation sources we have (until Jürgen cleans it...
Removed the milestone. This is a bigger item and just pushing it from one milestone to the next isn't going to help anything.
After eyeballing the code in both Zope 4 and Zope 2 the statement "Zope 4 assumes that the query string content is encoded via the configuration dependent zpublisher_default_encoding" appears to...
I have stepped through the code under Python 2 and it seems to do everything correctly. The input gets decoded using the character set you're explicitly passing in, and then...
I have a different interpretation of what `processInputs` is supposed to do. It is supposed to marshal input values into something that later processing code can reliably work with. When...
Quick update after some more debugging: Under Python 3 the `latin1`-encoded values are broken during the creation of the FieldStorage object: https://github.com/zopefoundation/Zope/blob/57da264fbcf1c0577470231208683b9d1b38de60/src/ZPublisher/HTTPRequest.py#L514-L515 FieldStorage knows nothing about the special marshaling identifier...
Dieter, I have seen you mention several times the use of `latin-1` as a "safe" way to decode bytes strings that may be in different encodings. I had never heard...
What exactly is the goal of this change?
> Maybe we should wait merging this PR until 3.11.0 final is released as 3.11 requires a new release of `RestrictedPython` which is currently just a dev release until we...
Two issues: - It looks like `versions-prod.cfg` wants to pull the alpha of `RestrictedPython` for Python 3.10. That's not right, correct? - There seems to be an issue with the...