Message 222344 - Python tracker

➜

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	vajrasky
Recipients	docs@python, gvanrossum, vajrasky, vstinner, yselivanov
Date	2014-07-05.08:45:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1404549913.45.0.543657172277.issue21921@psf.upfronthosting.co.za>
In-reply-to

Content
These examples coming from: https://docs.python.org/3/library/asyncio-eventloop.html#example-hello-world-callback and https://docs.python.org/3/library/asyncio-eventloop.html#example-set-signal-handlers-for-sigint-and-sigterm throw resource usage warning. One of them gives this output: Event loop running forever, press CTRL+c to interrupt. pid 3075: send SIGINT or SIGTERM to exit. ^Cgot signal SIGINT: exit sys:1: ResourceWarning: unclosed <socket object at 0x7f7124783448> sys:1: ResourceWarning: unclosed <socket object at 0x7f7124c230e8> The patch adds closing the loop code in the examples.

These examples coming from:
https://docs.python.org/3/library/asyncio-eventloop.html#example-hello-world-callback

and

https://docs.python.org/3/library/asyncio-eventloop.html#example-set-signal-handlers-for-sigint-and-sigterm

throw resource usage warning.

One of them gives this output:
Event loop running forever, press CTRL+c to interrupt.
pid 3075: send SIGINT or SIGTERM to exit.
^Cgot signal SIGINT: exit
sys:1: ResourceWarning: unclosed <socket object at 0x7f7124783448>
sys:1: ResourceWarning: unclosed <socket object at 0x7f7124c230e8>

The patch adds closing the loop code in the examples.

History
Date	User	Action	Args
2014-07-05 08:45:13	vajrasky	set	recipients: + vajrasky, gvanrossum, vstinner, docs@python, yselivanov
2014-07-05 08:45:13	vajrasky	set	messageid: <1404549913.45.0.543657172277.issue21921@psf.upfronthosting.co.za>
2014-07-05 08:45:13	vajrasky	link	issue21921 messages
2014-07-05 08:45:13	vajrasky	create