On Sun, Mar 01, 2020 at 12:17:30PM -0800, Gregory P. Smith wrote:
> FWIW that is a configure flag, not a flag to the compiler, so I see no
> problem with this. The default build has not changed, it just exposes
> another way to build the interpreter. We've done this in the past with
> things li
Enabling that workaround for embedders using threads without coroutines
while figuring out the real underlying contextvars issue seems like a
reasonable change to make in the maintenance branches.
Cheers,
Nick.
___
python-committers mailing list -- pytho
FWIW that is a configure flag, not a flag to the compiler, so I see no
problem with this. The default build has not changed, it just exposes
another way to build the interpreter. We've done this in the past with
things like --enable-optimizations and such flags.
In this case it appears to enable
I don't know. However, it seems possible given the symptoms of the
original issue (see ASAN-produced stack trace) that there is a bug when
using context vars with foreign threads (in this case, C++-created):
https://bugs.python.org/issue39776
Regards
Antoine.
Le 01/03/2020 à 11:30, Łukasz Lan
