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 Jim.Jewett
Recipients BreamoreBoy, Jim.Jewett, amaury.forgeotdarc, brian.curtin, dino.viehland, midnightdf, pitrou, r.david.murray, vstinner
Date 2014-06-20.18:22:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403288559.26.0.459256842955.issue8110@psf.upfronthosting.co.za>
In-reply-to
Content
It would be good to have the library work unchanged on both implementations.

If subprocess only failed later, it would be less good, as the stdlib would then set an example that doesn't actually succeed.

Note that the attached patch (by flox) does NOT implement the discussed "or" tests on sysm.platform; it instead checks whether _subprocess it importable.  Is the assumption of an accelerator module itself too implementation-specific?  I'm also not sure that the test in the patch isn't too broad -- is windows the only platform with _subprocess?  Because if not, then the new test would mess up logic later in the file, such as that at line 635 in Popen.__init__
History
Date User Action Args
2014-06-20 18:22:39Jim.Jewettsetrecipients: + Jim.Jewett, amaury.forgeotdarc, pitrou, vstinner, dino.viehland, r.david.murray, brian.curtin, midnightdf, BreamoreBoy
2014-06-20 18:22:39Jim.Jewettsetmessageid: <1403288559.26.0.459256842955.issue8110@psf.upfronthosting.co.za>
2014-06-20 18:22:39Jim.Jewettlinkissue8110 messages
2014-06-20 18:22:39Jim.Jewettcreate