➜

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 barry
Recipients Anthony Sottile, Chris Billington, Ivan.Pozdeev, Peter L3, SilentGhost, __Vano, barry, brett.cannon, cheryl.sabella, christian.heimes, eric.smith, eric.snow, ethan smith, ionelmc, jaraco, mhammond, ncoghlan, pitrou, steve.dower, takluyver, terry.reedy, veky
Date 2019-03-07.06:56:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <C3B646A8-724D-4B5A-990C-EB0F54E910E2@python.org>
In-reply-to <1551927899.06.0.914050581164.issue33944@roundup.psfhosted.org>
Content 
On Mar 6, 2019, at 19:04, Anthony Sottile <report@bugs.python.org> wrote:

> It assigns `subprocess.run`, which is an api in python3.5+.  In those versions, `subprocess.check_*` is implemented in terms of `subprocess.run`.   The `subprocess.run` provided by that package has a different api than the stdlib one so any use of the subprocess module is broken just by having that package installed

Doesn’t that kind of prove my point? :)
History
Date User Action Args
2019-03-07 06:56:21barrysetrecipients: + barry, mhammond, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, eric.smith, christian.heimes, ionelmc, SilentGhost, __Vano, eric.snow, takluyver, steve.dower, veky, Ivan.Pozdeev, Anthony Sottile, ethan smith, cheryl.sabella, Chris Billington, Peter L3
2019-03-07 06:56:21barrylinkissue33944 messages
2019-03-07 06:56:21barrycreate