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 martin.panter, vstinner
Date 2016-03-23.08:02:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ8YyWcQO3_qF=JsTr_ALCMJZM7z=D=VDj7e=4XGj=8aQ@mail.gmail.com>
In-reply-to <1458697946.92.0.922624292811.issue26612@psf.upfronthosting.co.za>
Content
Martin Panter added the comment:
> Wouldn’t it be better to fix the underlying problem with the test cases?

I don't feel able to fix AIX issues, and I don't think that we can fix
all issues. You still get ResourceWarning if you interrupt the test
with CTRL+c which is not a bug.

> Also, you can often use self.addCleanup(s.close), which saves a level of indentation (and associated noise in the annotate history).

It may work on some cases, but not all of them. And I like controlling
when a socket is closed: I prefer to close it inside the test, and not
sometime later with unittest magic features.

> Also remember that sockets don’t do context management in Python 2, so this would bring more incompatibilies when merging tests between the two branches.

Since this issue is not really a blocker bug, I suggest to only modify
Python 3.6.

It's a follow-up of all work on ResourceWarning (on Python 3.6) last days:
https://docs.python.org/dev/whatsnew/3.6.html#warnings
History
Date User Action Args
2016-03-23 08:02:05vstinnersetrecipients: + vstinner, martin.panter
2016-03-23 08:02:05vstinnerlinkissue26612 messages
2016-03-23 08:02:04vstinnercreate