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 r.david.murray
Recipients gvanrossum, jinty, r.david.murray, vstinner, yselivanov
Date 2015-10-28.14:49:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446043794.95.0.181430831888.issue25489@psf.upfronthosting.co.za>
In-reply-to
Content
Using sys.exit means you are depending on garbage collection to clean up all of your program's resources.  In the general case this is a bad idea.  A better design is to call loop.stop, and then do cleanup (which might involve calling some wait_closed functions via loop.run_until_complete).  If you just call sys.exit, your resources may not get cleaned up correctly, or may not get cleaned up correctly somewhat randomly due to the indeterminacies in the order in which garbage collection is done.  This may not matter for a simple program, but I find it makes it easier for me if I just do it "the right way" always :)
History
Date User Action Args
2015-10-28 14:49:55r.david.murraysetrecipients: + r.david.murray, gvanrossum, vstinner, yselivanov, jinty
2015-10-28 14:49:54r.david.murraysetmessageid: <1446043794.95.0.181430831888.issue25489@psf.upfronthosting.co.za>
2015-10-28 14:49:54r.david.murraylinkissue25489 messages
2015-10-28 14:49:54r.david.murraycreate