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 jaraco
Recipients ezio.melotti, jaraco, vstinner
Date 2014-07-06.14:39:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404657562.39.0.323212380566.issue21927@psf.upfronthosting.co.za>
In-reply-to
Content
Consider this simple example in Powershell (Windows 8.1):

C:\Users\jaraco> cat .\print-input.py
import sys
print(next(sys.stdin))

C:\Users\jaraco> echo foo | .\print-input.py
foo

The BOM (byte order mark) appears in the standard input stream. When using cmd.exe, the BOM is not present. This behavior occurs in CP1252 as well as CP65001.

I suspect that Python should be detecting/stripping and possibly honoring the BOM when decoding input on stdin.

This issue is present in Python 3.4.0 and Python 3.4.1. I have not tested other Python versions.
History
Date User Action Args
2014-07-06 14:39:22jaracosetrecipients: + jaraco, vstinner, ezio.melotti
2014-07-06 14:39:22jaracosetmessageid: <1404657562.39.0.323212380566.issue21927@psf.upfronthosting.co.za>
2014-07-06 14:39:22jaracolinkissue21927 messages
2014-07-06 14:39:21jaracocreate