Change by JustAnotherArchivist :
--
nosy: +JustAnotherArchivist
___
Python tracker
<https://bugs.python.org/issue42367>
___
___
Python-bugs-list mailin
New submission from JustAnotherArchivist :
The extension building does not respect the --jobs option passed to make.
Specifically, in that step, `python setup.py build` always spawns as many gcc
processes as there are CPU cores available regardless of that option. This
caused problems for me
Change by JustAnotherArchivist :
--
nosy: +JustAnotherArchivist
___
Python tracker
<https://bugs.python.org/issue18233>
___
___
Python-bugs-list mailin
Change by JustAnotherArchivist :
--
pull_requests: +20619
pull_request: https://github.com/python/cpython/pull/21474
___
Python tracker
<https://bugs.python.org/issue32
JustAnotherArchivist added the comment:
As another datapoint, this also broke some of my code on 3.8 because I was
using `concurrent.futures.CancelledError` rather than `asyncio.CancelledError`
to handle cancelled futures. And I'm certainly not the only one to have done
this given that
New submission from JustAnotherArchivist :
While the situation is clear regarding coroutine objects (#25887), as far as I
can see, the documentation doesn't specify whether asyncio.Futures can be
awaited multiple times. The code has always (at least since the integration
into CP