Message145540
| Author |
eric.araujo |
| Recipients |
amaury.forgeotdarc, eric.araujo, loewis, runtux, tarek, techtonik, vstinner |
| Date |
2011年10月14日.15:53:41 |
| SpamBayes Score |
1.460531e-08 |
| Marked as misclassified |
No |
| Message-id |
<1318607622.56.0.190959131654.issue10945@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
>> It is not code under the users’ control (i.e. setup.py)
>> that uses MBCS, but the bdist_wininst command itself.
> bdist_command append configuration data to a wininst-xxx.exe binary.
Are you sure? The string that’s encoded with mbcs comes from the get_inidata method in bdist_wininst.py; get_inidata only works with strings (either string literals or str objects (in 3.x) given as attributes of the command object or in the DistributionMetadata object).
> Where does this file come from? Can we modify wininst-xxx.exe binaries?
If needed, we can: the code lives in PC/bdist_wininst.
> Use the ASCII encoding is the safest solution
I don’t think so. Distutils supports author='Éric', so bdist_wininst should too :) |
|