On 12/09/2014 04:28, Stephen J. Turnbull wrote:
Jeff Allen writes:
> A welcome article. One correction should be made, I believe: the area of
> code point space used for the smuggling of bytes under PEP-383 is not a
> "Unicode Private Use Area", but a portion of the trailing surrogate
>
Jeff Allen writes:
> A welcome article. One correction should be made, I believe: the area of
> code point space used for the smuggling of bytes under PEP-383 is not a
> "Unicode Private Use Area", but a portion of the trailing surrogate
> range.
Nice catch. Note that the surrogate range
On Tue, 9 Sep 2014 08:20:52 +1000
Nick Coghlan wrote:
> On 9 Sep 2014 04:00, "Barry Warsaw" wrote:
> > >
> > >This would need to be updated first, once it *did* take such an argument,
> > >this would be accomplished by:
> > >
> > >context = ssl.create_default_context()
> > >context.verify_mode =
On Mon, 8 Sep 2014 10:44:51 -0700
Alex Gaynor wrote:
> *Shifts uncomfortably* it looks like presently there's not a good way to
> change anything about the SSL configuration for urllib.request.urlopen. It
> does not take a `context` argument, as the http.client API does:
> https://docs.python.org/
A welcome article. One correction should be made, I believe: the area of
code point space used for the smuggling of bytes under PEP-383 is not a
"Unicode Private Use Area", but a portion of the trailing surrogate
range. This is a code violation, which I imagine is why
"surrogateescape" is an er
