M.-A. Lemburg mal at egenix.com
Wed Feb 15 19:02:58 CET 2006

• Previous message: [Python-Dev] str object going in Py3K
• Next message: [Python-Dev] str object going in Py3K
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Barry Warsaw wrote:
> On Wed, 2006-02-15 at 18:29 +0100, M.-A. Lemburg wrote:
> 
>> Maybe a weird idea, but why not use static methods on the
>> bytes and str type objects for this ?!
>>
>> E.g. bytes.openfile(...) and unicode.openfile(...) (in 3.0
>> renamed to str.openfile())
> 
> That's also not a bad idea, but I'd leave off one or the other of the
> redudant "open" and "file" parts.  E.g. bytes.open() and unicode.open()
> seem fine to me (we all know what 'open' means, right? :).

Thinking about it, I like your idea better (file.bytes()
and file.text()).

Anyway, as long as we don't start adding openthis() and openthat()
I guess I'm happy ;-)

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 15 2006)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

---

• Previous message: [Python-Dev] str object going in Py3K
• Next message: [Python-Dev] str object going in Py3K
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list