Seth Michael Larson added the comment:
Leaving a thought here, I'm highlighting that we're now implementing two
different standards, RFC 3986 with hints of WHATWG-URL. There are pitfalls to
doing so as now a strict URL parser for RFC 3986 (like the one used by
urllib3/requests) will give
Changes by Seth Michael Larson <sethmichaellar...@protonmail.com>:
--
components: +asyncio
nosy: +gvanrossum
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
New submission from Seth Michael Larson:
Copied from https://github.com/python/asyncio/issues/484
"""
>From https://bugs.python.org/issue23242#msg284930
The following script is used to reproduce the bug:
import asyncio
async def execute():
process = await asyncio.crea
Seth Michael Larson added the comment:
Sorry for making noise, yes I was using the implementation in Python 2.x. I
will do better investigation in the future.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Seth Michael Larson:
The socket.socketpair() fallback for Python 3.5+ is incorrectly implemented
from the original source. The fallback doesn't provide a backlog argument to
the lsock.listen() function call.
When running the function it gives the following error
