STINNER Victor added the comment:

> We may also use support.TESTFN_UNDECODABLE
> in test_cmd_line_script.test_non_ascii() on Windows

Oh, subprocess doesn't support passing bytes arguments to a program anymore 
(since Python 3.0).

So it's better to use TESTFN_NONASCII instead for this test ;-) It confirms 
that we need two constants depending on the context. It dependson the platform 
and how the data is read/written: sometimes undecodable characters are 
supported on any platform (ex: base64 encoder), sometimes undecodable 
characters are not supported (ex: distutils expects valid metadata), sometimes 
it depends on the platform (ex: this test).


Python tracker <>
Python-bugs-list mailing list

Reply via email to