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 exarkun
Recipients JPosthuma, benjamin.peterson, djarb, exarkun, giampaolo.rodola, intgr, janssen, josiah.carlson, josiahcarlson, r.david.murray
Date 2009-07-13.15:50:45
SpamBayes Score 6.5114025e-12
Marked as misclassified No
Message-id <1247500247.15.0.267895204685.issue1563@psf.upfronthosting.co.za>
In-reply-to
Content
> It's not, I was more thinking of push_str(foo), where it uses a
default encoding. I think some people don't know what unicode or
encoding is, or don't want to worry about it.

Nice as it sounds, the problem with this is that those people cannot
write correct programs without understanding this.  A push_str API which
implicitly encodes unicode to str would just be a point for bugs to be
introduced.
History
Date User Action Args
2009-07-13 15:50:47exarkunsetrecipients: + exarkun, josiahcarlson, janssen, giampaolo.rodola, djarb, josiah.carlson, benjamin.peterson, r.david.murray, intgr, JPosthuma
2009-07-13 15:50:47exarkunsetmessageid: <1247500247.15.0.267895204685.issue1563@psf.upfronthosting.co.za>
2009-07-13 15:50:45exarkunlinkissue1563 messages
2009-07-13 15:50:45exarkuncreate