11.08.18 23:08, Santiago Basulto пише:
Hello folks! I'm using the `concurrent.futures.ProcessPoolExecutor` with
a couple of functions that have been decorated with a class decorator.
Both `concurrent.futures` and `multiprocessing` breaks because "the
object's can't be pickled". There's a
Hello folks! I'm using the `concurrent.futures.ProcessPoolExecutor` with a
couple of functions that have been decorated with a class decorator. Both
`concurrent.futures` and `multiprocessing` breaks because "the object's
can't be pickled". There's a really simple fix for this, which is just,
Petr Viktorin schrieb am 10.08.2018 um 13:48:
> Would this be better than a flag + raising an error on init?
Ok, I've implemented this in Cython for now, to finally move the PEP-489
support forward. The somewhat annoying drawback is that module reloading
previously *seemed* to work, simply
Antoine Pitrou schrieb am 11.08.2018 um 15:19:
> On Fri, 10 Aug 2018 19:15:11 +0200 Armin Rigo wrote:
>> Currently, the C API only allows Psyco-style JITting (much slower than
>> PyPy). All three other points might not be possible at all without a
>> seriously modified C API. Why? I have no
Hi Armin,
On Fri, 10 Aug 2018 19:15:11 +0200
Armin Rigo wrote:
> Currently, the C API only allows Psyco-style JITting (much slower than
> PyPy). All three other points might not be possible at all without a
> seriously modified C API. Why? I have no proof, but only
> circumstantial
> Would this be better than a flag + raising an error on init?
Exactly. PEP 489 only says "Extensions using the new initialization
scheme are expected to support subinterpreters". What's wrong with
raising an exception when the module is initialized the second time?
Jeroen.
