[Python-ideas] Why decode()/encode() name is harmful
anatoly techtonik
techtonik at gmail.com
Mon Jun 1 17:46:34 CEST 2015
On Sat, May 30, 2015 at 3:18 AM, Steven D'Aprano <steve at pearwood.info> wrote:
>
> As far as I can see, he has been given the solution, or at least a
> potential solution, on python-list, but as far as I can tell he either
> hasn't read it, or doesn't like the solutions offerred and so is
> ignoring them.
Let me update you on this. There was no solution given. Only the
pointers to go read some pointers on the internets again. So, yes,
I read replies. But I have very little time to analyse and follow up.
The idea I wanted to convey in this thread is that encode/decode
is confusing, so if you agree with that, I can start to propose
alternatives.
And just to make you understand the importance of the question
with translating from bytes to unicode and back, let me just tell
that this question is the third one voted with 221k views on SO in
Python 3 tag.
http://stackoverflow.com/questions/tagged/python-3.x
--
anatoly t.
More information about the Python-ideas
mailing list