[Python-Dev] bytes.from_hex() [Was: PEP 332 revival in coordination with pep 349?] (original) (raw)
Bob Ippolito bob at redivi.com
Sat Feb 18 02:12:17 CET 2006
- Previous message: [Python-Dev] bytes.from_hex() [Was: PEP 332 revival in coordination with pep 349?]
- Next message: [Python-Dev] bytes.from_hex()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 17, 2006, at 4:20 PM, Martin v. Löwis wrote:
Ian Bicking wrote:
Maybe it isn't worse, but the real alternative is:
import zlib import base64 base64.b64encode(zlib.compress(s)) Encodings cover up eclectic interfaces, where those interfaces fit a basic pattern -- data in, data out. So should I write 3.1415.encode("sin") or would that be 3.1415.decode("sin") What about "http://www.python.org".decode("URL") It's "data in, data out", after all. Who needs functions?
Well, 3.1415.decode("sin") is of course NaN, because 3.1415.encode ("sinh") is not defined for numbers outside of [-1, 1] :)
-bob
- Previous message: [Python-Dev] bytes.from_hex() [Was: PEP 332 revival in coordination with pep 349?]
- Next message: [Python-Dev] bytes.from_hex()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]