OK, we can just tell people who ask that the variable was moved. (Or they can figure it out from the source. :-)
On Wed, Feb 26, 2014 at 1:11 PM, Victor Stinner <[email protected]>wrote: > Even with my patch, it works if you modify the asyncio.coroutines._DEBUG. > It's just that the variable moved to a new module. > > For the RC2, you can modify the variable but I prefer to document the > environment variable. > > Victor > > Le mercredi 26 février 2014, Guido van Rossum <[email protected]> a écrit : > > But it was documented in the past, and it did work in 3.4rc2. Is there no >> way to still support it? >> >> >> On Wed, Feb 26, 2014 at 2:52 AM, Victor Stinner <[email protected] >> > wrote: >> >>> 2014-02-25 20:33 GMT+01:00 Guido van Rossum <[email protected]>: >>> >> What can be done to simplify merges from Tulip into Trollius: >>> >> >>> >> - create also asyncio.coroutines in Tulip >>> >> - replace "unittest.mock" with "mock" in all unit tests >>> >> - add also the COPYING file? >>> > >>> > All three of these sound fine. >>> >>> Here is a patch moving code to a new asyncio.coroutines module: >>> https://codereview.appspot.com/68940045 >>> >>> It moves also the private _DEBUG variable. This variable is no >>> documented since I added the new PYTHONASYNCIODEBUG environment >>> variable. I don't think that moving private variables break backward >>> compatibility. >>> >>> Victor >>> >> >> >> >> -- >> --Guido van Rossum (python.org/~guido) >> > -- --Guido van Rossum (python.org/~guido)
