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 pablogsal
Recipients gregory.p.smith, izbyshev, kevans, koobs, nanjekyejoannah, pablogsal, serhiy.storchaka, vstinner
Date 2019-01-16.22:35:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> One of the issue that I have with using posix_spawn() is that the *exact* behavior of subprocess is not properly defined by test_subprocess. Should we more more tests, or document that the exact behavior is "an implementation detail"? I guess that the best for users is get the same behavior on all platforms, but can we really warranty that? Python rely on the operating system and the libc, but each platform has subtle behavior differneces. Handling time and date is a good example: strptime() and strftime() have big differences between platforms. posix_spawn() is another example where the implementation is very different depending on the platform.

I don't think we can get the same behaviour in all platforms, but I would want to know what Gregory P. Smith thinks about this potential divergence in behaviour and what are the guarantees that posix_subprocess should maintain.
Date User Action Args
2019-01-16 22:35:32pablogsalsetrecipients: + pablogsal, gregory.p.smith, vstinner, serhiy.storchaka, koobs, izbyshev, nanjekyejoannah, kevans
2019-01-16 22:35:31pablogsalsetmessageid: <>
2019-01-16 22:35:31pablogsallinkissue35537 messages
2019-01-16 22:35:31pablogsalcreate