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 larry
Recipients gvanrossum, larry, pitrou, vstinner
Date 2013-12-02.20:07:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386014827.92.0.897593080077.issue19860@psf.upfronthosting.co.za>
In-reply-to
Content
Since this is a new library in 3.4, I can be more flexible.  And since you're talking about adding a new feature (rather than changing or removing an existing feature), this has a vanishingly small chance of screwing anything up.  Therefore I'm okay with adding this feature.

I suppose Python 3.4 only supports platforms that auto-close sockets at the end of a process, but I dimly recall Windows 95/98/ME didn't do that.  And there are crazy people porting to platforms like Amiga.  And I can hardly disapprove of something as wholesome as making sure people call .close().  So if Guido says okay, go ahead and check it in.
History
Date User Action Args
2013-12-02 20:07:07larrysetrecipients: + larry, gvanrossum, pitrou, vstinner
2013-12-02 20:07:07larrysetmessageid: <1386014827.92.0.897593080077.issue19860@psf.upfronthosting.co.za>
2013-12-02 20:07:07larrylinkissue19860 messages
2013-12-02 20:07:07larrycreate