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 vstinner
Recipients gvanrossum, oconnor663, vstinner, yselivanov
Date 2015-03-01.13:26:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbqjuVH1pXuhZy-_aEcgJ-Pto8MVG0t614P7=jBd-WFYg@mail.gmail.com>
In-reply-to <1425164650.51.0.613407013148.issue23548@psf.upfronthosting.co.za>
Content
I'm aware of the issue but I would prefer to not fix it.

The first problem is that you didn't close the event loop. I modified
recently the doc to explain at the begining that you should develop in the
debug mode. In this mode, you will see a warning if you don't close
explicitly the event loop.

The signal issue is that the event loop is closed very late during Python
finalization, and attributes of the signal module are already cleared.

Are you ok to not workaround this specific issue?

Closing an event loop implicitly late can lead to other various bugs.
History
Date User Action Args
2015-03-01 13:26:49vstinnersetrecipients: + vstinner, gvanrossum, yselivanov, oconnor663
2015-03-01 13:26:49vstinnerlinkissue23548 messages
2015-03-01 13:26:49vstinnercreate