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 lambacck
Recipients belopolsky, catherine, doerwalter, eric.araujo, ezio.melotti, georg.brandl, gpolo, lambacck, orsenthil, pitrou, r.david.murray, rhettinger, ron_adam, vstinner
Date 2011-08-07.15:13:36
SpamBayes Score 1.4505112e-05
Marked as misclassified No
Message-id <1312730017.28.0.911345962796.issue10087@psf.upfronthosting.co.za>
In-reply-to
Content
Senthil: I wasn't advocating the removal of the ability to specify encoding, only stating that avoiding the use of sys.stdout.buffer.write could only sensibly be done if we also removed the ability to specify an encoding (I can see how my wording might have been confusing). Earlier (msg122219) I said that we probably can't remove the encoding option because that would break backwards compatibility.

FWIW, I think that the encoding parameter to the console program is probably sensible because there are no guarantees that the sys.getdefaultencoding() is actually set to the console encoding and I would guess that most people using the html option are not sending output to the console anyway. They are likely redirecting the output somewhere else because there is no "output this to a file" option.
History
Date User Action Args
2011-08-07 15:13:37lambaccksetrecipients: + lambacck, doerwalter, georg.brandl, rhettinger, belopolsky, orsenthil, pitrou, vstinner, ron_adam, gpolo, ezio.melotti, eric.araujo, r.david.murray, catherine
2011-08-07 15:13:37lambaccksetmessageid: <1312730017.28.0.911345962796.issue10087@psf.upfronthosting.co.za>
2011-08-07 15:13:36lambaccklinkissue10087 messages
2011-08-07 15:13:36lambacckcreate