Changes by STINNER Victor victor.stin...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22480
___
___
STINNER Victor added the comment:
I created a more specific issue for destructortest.py: issue #22599. It's not
directly related to asyncio.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22480
New submission from chrysn:
the attached test.py snipplet, which runs an asyncio main loop to the
completion of a coroutine raising SystemExit, runs cleanly when invoked using
`python3 test.py`, but shows a logging error from the Task.__del__ method when
invoked using `python3 -m test`.
the
Changes by chrysn chr...@fsfe.org:
Added file: http://bugs.python.org/file36707/test.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22480
___
___
Changes by chrysn chr...@fsfe.org:
Added file: http://bugs.python.org/file36708/test.err
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22480
___
___
Changes by chrysn chr...@fsfe.org:
Added file: http://bugs.python.org/file36709/destructortest.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22480
___
STINNER Victor added the comment:
Running python test.py and python -m test changes how the code is loaded.
With python test.py, test.py becomes the __main__ module, whereas python
-m test uses the test module.
At Python exit, the __main__ module and other modules are destroyed differently.
