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 ammar2
Recipients Michel Desmoulin, ammar2, ncoghlan, r.david.murray, vstinner, xtreak, yselivanov
Date 2019-10-21.17:44:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I did a quick search to see what code would break from sys.argv[0] going relative

  intext:"sys.argv[0]" ext:py"sys.argv%5B0%5D"

and while most uses of it are to print usage messages. There is potentially code relying on it being a relative path that will break from this change:


I think Michel and Nick are correct here and the status-quo should be maintained for sys.argv[0]. Michel should not have to enumerate the use cases for a relative sys.argv[0].
Date User Action Args
2019-10-21 17:44:21ammar2setrecipients: + ammar2, ncoghlan, vstinner, r.david.murray, yselivanov, Michel Desmoulin, xtreak
2019-10-21 17:44:21ammar2setmessageid: <>
2019-10-21 17:44:21ammar2linkissue20443 messages
2019-10-21 17:44:21ammar2create