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 martin.panter
Recipients akira, juj, martin.panter, vstinner
Date 2015-06-02.02:48:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree with the deprecation idea. The parameter checking logic doesn’t seem right though; see Reitveld. Also, I would have made the warning specify exactly what is deprecated, in case the stack trace doesn’t identify the function, which I think would always happen with check_call(). Also be less specific about future changes, unless there is clear consensus to make this change in 3.6. Maybe something like:

"Passing PIPE to call() and check_call() is deprecated; use DEVNULL instead to discard output or provide empty input"

Since 3.5 is now in the beta phase, would adding this deprecation be allowed, or should it be deferred to the 3.6 branch? Also, I’m not sure what the policy is for Python 2. Maybe it would be acceptable as a Python 3 compatibility warning, triggered by the “python2 -3” option; I dunno.
Date User Action Args
2015-06-02 02:48:42martin.pantersetrecipients: + martin.panter, vstinner, akira, juj
2015-06-02 02:48:42martin.pantersetmessageid: <>
2015-06-02 02:48:42martin.panterlinkissue22442 messages
2015-06-02 02:48:41martin.pantercreate