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 ned.deily
Recipients Daniel.Farina, berker.peksag, ned.deily
Date 2013-06-11.21:26:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370985965.36.0.164760110369.issue18186@psf.upfronthosting.co.za>
In-reply-to
Content
Your proposed change would still not make the source compatible with Python 2.2 (released over a decade ago) as set() was introduced in 2.4. When the subprocess module was introduced back then, it made sense to maintain compatibility with then-recent releases but it no longer makes sense when Python 2.7 is reaching the end of its life and all previous versions of Python 2 are retired or no longer receive bug fixes.  In Python 3, a number of these compatibility claims have been removed from the source, including the one in subprocess.  We could do a comment cleanup in the Python 2 source, as well, but at this point it hardly seems worth it.  And since we do no testing against previously retired releases, making this code change is no guarantee that the module would really work in any previous version of Python 2.x.  That's for you to decide if you are backporting to these unsupported versions.
History
Date User Action Args
2013-06-11 21:26:05ned.deilysetrecipients: + ned.deily, berker.peksag, Daniel.Farina
2013-06-11 21:26:05ned.deilysetmessageid: <1370985965.36.0.164760110369.issue18186@psf.upfronthosting.co.za>
2013-06-11 21:26:05ned.deilylinkissue18186 messages
2013-06-11 21:26:05ned.deilycreate