Author pitrou
Recipients cvrebert, docs@python, eli.bendersky, eric.araujo, ezio.melotti, flox, nadeem.vawda, ncoghlan, paul.moore, pitrou, vstinner
Date 2012-02-12.14:53:11
SpamBayes Score 1.2826e-08
Marked as misclassified No
Message-id <1329058207.3456.2.camel@localhost.localdomain>
In-reply-to <1329048996.28.0.292415350086.issue13997@psf.upfronthosting.co.za>
Content
> My mental model here is text editors, which let you open any file, do
> their best to display as much as they can and allow you to manipulate
> it without damaging the bits you don't change. I don't see any reason
> why people shouldn't be able to write Python 3 code that way if they
> need to.

Some text editors try to guess the encoding, which is different from
"display invalid characters anyway".
Other text editors like gedit pop up an error when there are invalid
bytes according to the configured encoding.

That said, people *are* able to write Python 3 code the way you said.
They simply have to use the "surrogateescape" error handler.
History
Date User Action Args
2012-02-12 14:53:12pitrousetrecipients: + pitrou, paul.moore, ncoghlan, vstinner, nadeem.vawda, ezio.melotti, eric.araujo, eli.bendersky, cvrebert, flox, docs@python
2012-02-12 14:53:11pitroulinkissue13997 messages
2012-02-12 14:53:11pitroucreate