[issue6141] missing first argument on subprocess.Popen w/ executable
New submission from Lie Ryan lie.1...@gmail.com: Following from http://comments.gmane.org/gmane.comp.python.tutor/55576 import subprocess subprocess.Popen(['a', 'b', 'c', 'd'], executable='echo') subprocess.Popen object at 0x7fdf7bb2bd50 b c d instead of the (what I) expected result a b c d I suggests two possible change: 1. add another optional argument called displayed_executable (or something similar) and make the arg argument contains only arguments 2. it is made clear in the documentation that the first argument is used as executable display name Since the first alternative is behavioral change, it couldn't possibly go through already released version; therefore if it is the chosen solution it would have to go to Python 2.7 and Python 3.2. Changing the documentation should be easier, although the problem will persist for unsuspecting users; and even if the first alternative is taken, perhaps documentation change should still be done retrospectively (I don't know the policy on doc change on old python version) It should be noted that I tested this only with Python 2.5 on Gentoo (although from the discussion, I presumed this is considered a feature and would have persisted in later versions). And at the time of this writing, I have no idea how it behaves in Windows. -- assignee: georg.brandl components: Documentation, Library (Lib) messages: 88504 nosy: georg.brandl, lieryan severity: normal status: open title: missing first argument on subprocess.Popen w/ executable type: behavior versions: Python 2.5, Python 2.6, Python 2.7, Python 3.0, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6141] missing first argument on subprocess.Popen w/ executable
R. David Murray rdmur...@bitdance.com added the comment: The way it works is the way most programmers expect it to work, even though most get bitten by it more than once. So the behavior isn't going to change. I've attached a doc fix, but I'm not sure whether or not the 'diplay name' piece applies only to unix, although I've documented it that way. The windows documentation I found for CreateProcess does not mention it, though it does note that most C programmers treat argv[0] as the process name, consistent with the way subprocess handles the argument string. The Windows documentation I consulted is here: http://msdn.microsoft.com/en-us/library/ms682425.aspx -- keywords: +patch nosy: +r.david.murray priority: - normal versions: -Python 2.5 Added file: http://bugs.python.org/file14111/issue6141-doc.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6141] missing first argument on subprocess.Popen w/ executable
Georg Brandl ge...@python.org added the comment: Patch looks good, just replace `ps` by :program:`ps` please. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6141] missing first argument on subprocess.Popen w/ executable
R. David Murray rdmur...@bitdance.com added the comment: Fixed in r73026, thanks. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
