Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Jan 3, 2007, at 1:44 PM, Josiah Carlson wrote:
>
> > What about:
> >
> > 'hello world'.encode.base64()
> >
> > Then incorrectly named encodings can raise an attribute error. Users
> > can discover what they can encode/decode their objects to via dir
> > (obj.encode),
> > etc.
>
> 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().
- Josiah
_______________________________________________
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
