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 tim.golden
Recipients amaury.forgeotdarc, andersjm, brotch, gregcouch, jnoller, kcwu, mclausch, ocean-city, terry.reedy, tim.golden, xianyiteng
Date 2010-08-08.17:26:01
SpamBayes Score 0.00040810416
Marked as misclassified No
Message-id <1281288365.99.0.0328857080064.issue1759845@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-08-08 17:26:06tim.goldensetrecipients: + tim.golden, terry.reedy, amaury.forgeotdarc, gregcouch, andersjm, ocean-city, mclausch, brotch, kcwu, jnoller, xianyiteng
2010-08-08 17:26:05tim.goldensetmessageid: <1281288365.99.0.0328857080064.issue1759845@psf.upfronthosting.co.za>
2010-08-08 17:26:02tim.goldenlinkissue1759845 messages
2010-08-08 17:26:01tim.goldencreate