Message241465
| Author |
vstinner |
| Recipients |
paul.moore, piotr.dobrogost, r.david.murray, steve.dower, tim.golden, vstinner, zach.ware |
| Date |
2015年04月18日.23:03:01 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1429398181.68.0.372201355291.issue23901@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
If sys.stdout is modified, it must be carefully tested in various scenario:
- Windows console, default config
- Windows console, TrueType font
- PowerShell => see #21927, it looks like PowerShell has its own set of Unicode issues
- Redirect output into a file
- etc.
Very good articles by Michael S. Kaplan on Windows stdout/console:
- "Conventional wisdom is retarded, aka What the @#%&* is _O_U16TEXT?"
http://www.siao2.com/2008/03/18/8306597.aspx
- "Myth busting in the console"
http://www.siao2.com/2010/10/07/10072032.aspx
- "Cunningly conquering communicated console caveats. Comprende, mon Capitán?"
http://www.siao2.com/2010/05/07/10008232.aspx
See also fwide() function.
Good luck... |
|