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 r.david.murray
Recipients Alexander.Belopolsky, Arfrever, asvetlov, brian.curtin, csernazs, cvrebert, dstanek, eric.araujo, eric.smith, giampaolo.rodola, holdenweb, larry, ncoghlan, r.david.murray, vstinner
Date 2012-04-05.20:02:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
No, you need to be able to pass bytes to Popen, just like you do to the os.exec[xx] functions.  When the OS doesn't fully support unicode, that is sometimes the only option.  As for filenames; again, as long as the underlying systems use bytes filenames we need to support it.  Currently we encode them when received using surrogateescape and decode them back to bytes when used. 

I am not sure what os.exec[xx] does with strings containing non-ascii.  Presumably it uses some default encoding or other, which seems to be utf-8 on my system.  (It doesn't seem to be explicitly documented where those functions are discussed in the os module.)
Date User Action Args
2012-04-05 20:02:40r.david.murraysetrecipients: + r.david.murray, holdenweb, csernazs, ncoghlan, vstinner, dstanek, larry, eric.smith, giampaolo.rodola, eric.araujo, Arfrever, brian.curtin, cvrebert, asvetlov, Alexander.Belopolsky
2012-04-05 20:02:40r.david.murraysetmessageid: <>
2012-04-05 20:02:39r.david.murraylinkissue7839 messages
2012-04-05 20:02:39r.david.murraycreate