This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients boytsovea, gregory.p.smith, mark.dickinson, rhettinger, skrah
Date 2020-03-02.11:01:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If someone builds an interpreter with this configure flag, does it break
> compatibility with anything that code may have started to expect as of 3.7?

Yes, anything that relies on the implicit context being coroutine-safe
does not work.  The only test that expectedly breaks in the stdlib is:


Basically you can't use operators inside coroutines in the same thread
if both coroutines use a different implicit context.

You can of course replace all operators inside coroutines by the
corresponding context methods:

   # Unsafe with TLS context:
   async def foo():
       with localcontext(Context(prec=10)):
           x = Decimal(1) / 9

   # Safe, just avoid the TLS context:
   async def foo():
       c = Context(prec=10)
       x = c.divide(Decimal(1), 9)
Date User Action Args
2020-03-02 11:01:22skrahsetrecipients: + skrah, rhettinger, gregory.p.smith, mark.dickinson, boytsovea
2020-03-02 11:01:22skrahsetmessageid: <>
2020-03-02 11:01:22skrahlinkissue39794 messages
2020-03-02 11:01:22skrahcreate