-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 3, 2007, at 3:48 PM, Josiah Carlson wrote:
>> That's better. I'm not sure it's a total win over what we have now,
>> unless you're thinking that the mapping between .encode.<whatever>
>> and .encode('whatever') is automatic.
>
> I'm thinking that .encode('whatever') would disappear (maybe be
> deprecated for 2.x if it was seen as a solution to long-standing
> issues),
> to be replaced by .encode.whatever().
Hmm, that does sound interesting. Sometimes you have a string that
names the encoding, such as when you get it from an email header.
Other times you know what function you want to call, such as is
usually the case with base64 and friends. OTOH, the former can
always be handled with getattr().
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZwZFXEjvBPtnXfVAQJOtAQAnQxa0iO9vMBfydR/Hx8rDIzJR8vVUvOY
lstDTS8EqW8I46C9Az01s+uVlx5bNgnEaKaPm4Q6VSZZZZi3Eaxz9VWRbOXec9iQ
lLoBAOyCo6mwz/GBv2sDp7dUM5hzhU/stETcWnSYXNqZpcV7uStSSSfsrxUhzl6D
CXs6qGddVvg=
=DfGN
-----END PGP SIGNATURE-----
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
