> "\x01\x02".encode('zlib') for instance is a bytes to bytes operation.
I think the inclusion of things like zlib (or rot13 or whatever) was a conceptual error that just fosters confusion.
Re:Why Python 3 Exists
by the_mitsuhiko on Thursday December 17, 2015 @03:53PM
(#10754465)
> I think the inclusion of things like zlib (or rot13 or whatever) was a conceptual error that just fosters confusion.
We should not optimize languages for idiots. There is nothing confusing about such an operation for anyone who can use their brain. Python 3 still contains those operations but instead of x.encode(y) you now do encode(x, y).
The principle of least astonishment and optimizing for idiocy are not the same thing.
Re:Why Python 3 Exists
by the_mitsuhiko on Friday December 18, 2015 @04:38AM
(#10757573)
How is an attribute error clearer than an exception that says something like: operation does not make sense of this type?
"\x01\x02".encode('zlib') is a really odd API. Just making sure: this is a real thing, and you're in favor of it?
It is in Python 2, but not in Python 3, where str.encode() and bytes.decode() have been restricted to only convert between strings and bytes.
>>> "foo".encode('zlib')
LookupError: 'zlib' is not a text encoding; use codecs.encode() to handle arbitrary codecs
Re:Why Python 3 Exists
by the_mitsuhiko on Thursday December 17, 2015 @03:54PM
(#10754473)
> "\x01\x02".encode('zlib') is a really odd API. Just making sure: this is a real thing, and you're in favor of it?
Of course this is a real thing and it's very frequently used. Yes I am in favour of it as the codec system in Python is precisely the place where things like this should live.
But then function would do something completely different. "\x01\x02".encode('zlib') for instance is a bytes to bytes operation. The problem is that "foo".encode('utf-8') does not give you an exception. If the coercion would not be enabled you would get an error:
That's not any worse than what Python 3 does: