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 simon mackenzie
Recipients SilentGhost, docs@python, gregory.p.smith, simon mackenzie
Date 2019-08-15.12:52:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGG2XGeMwcVzJwtxUJeN4B_4zCFrij-tFtDF_zTsmMbNBdWTwA@mail.gmail.com>
In-reply-to <1565873223.59.0.22231409286.issue37867@roundup.psfhosted.org>
Content
Technically true but I am not the first person to have incorrectly
interpreted this that it can be a string which suggests it is not clear to
the reader. Maybe should be explicitly stated in the description of run as
it is not obvious or intuitive.

On Thu, 15 Aug 2019 at 13:47, SilentGhost <report@bugs.python.org> wrote:

>
> SilentGhost <ghost.adh@runbox.com> added the comment:
>
> The only place this phrase appears is in CompletedProcess.args description
> and it is correct there. Whether args arguments of subprocess.run (or
> generally Popen) can be a list or a string is discussed in Frequently Used
> Arguments section, and it is perfectly clear from reading the text under
> which condition you can pass a string as args argument. I don't think
> anything needs fixing, both implementation and docs are correct.
>
> ----------
> assignee:  -> docs@python
> components: +Documentation
> nosy: +SilentGhost, docs@python
> type:  -> behavior
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue37867>
> _______________________________________
>
History
Date User Action Args
2019-08-15 12:52:56simon mackenziesetrecipients: + simon mackenzie, gregory.p.smith, SilentGhost, docs@python
2019-08-15 12:52:56simon mackenzielinkissue37867 messages
2019-08-15 12:52:56simon mackenziecreate