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 eggy
Recipients eggy
Date 2009-06-11.18:26:41
SpamBayes Score 0.019004777
Marked as misclassified No
Message-id <1244744803.37.0.794266933913.issue6268@psf.upfronthosting.co.za>
In-reply-to
Content
>>> f = open('foo', 'wt+', encoding='UTF-16')
>>> f.write('spam ham eggs')
13
>>> f.seek(0)
0
>>> f.read()
'spam ham eggs'
>>> f.seek(0)
0
>>> f.read()
'\ufeffspam ham eggs'

Although the BOM character is a ZERO WIDTH NO-BREAK SPACE, and should
therefore not impose many problems, the behavior is inconsistent and
unexpected.
codecs.open in 2.x suffers from this same behavior.
History
Date User Action Args
2009-06-11 18:26:43eggysetrecipients: + eggy
2009-06-11 18:26:43eggysetmessageid: <1244744803.37.0.794266933913.issue6268@psf.upfronthosting.co.za>
2009-06-11 18:26:41eggylinkissue6268 messages
2009-06-11 18:26:41eggycreate