Message113288
To confirm the situation on 3.x: a unicode string with non-ascii-encodable characters is fine. The easy test here in the uk is a pound sign:
<code>
import subprocess
FILENAME = "abc£.bat"
FILENAME.encode ("ascii")
#
# UnicodeEncodeError
#
with open (FILENAME, "w") as f:
f.write ("echo hello\n")
subprocess.call ([FILENAME])
#
# "hello" output as expected
#
</code>
So no action for 3.x. I'm sympathetic (in principle) to making a change to 2.7 but I haven't looked over the "competing" patches and assessed the ins-and-outs. |
|
Date |
User |
Action |
Args |
2010-08-08 17:26:06 | tim.golden | set | recipients:
+ tim.golden, terry.reedy, amaury.forgeotdarc, gregcouch, andersjm, ocean-city, mclausch, brotch, kcwu, jnoller, xianyiteng |
2010-08-08 17:26:05 | tim.golden | set | messageid: <1281288365.99.0.0328857080064.issue1759845@psf.upfronthosting.co.za> |
2010-08-08 17:26:02 | tim.golden | link | issue1759845 messages |
2010-08-08 17:26:01 | tim.golden | create | |
|