[Python-Dev] Re: file() or open()? (original) (raw)
Bob Ippolito bob at redivi.com
Sat Jul 10 01:54:19 CEST 2004
- Previous message: [Python-Dev] Re: file() or open()?
- Next message: [Python-Dev] Re: Re: file() or open()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jul 7, 2004, at 4:49 PM, orbitz wrote:
Terry Reedy wrote:
"François Pinard" <pinard at iro.umontreal.ca> wrote in message news:20040707183033.GA30577 at alcyon.progiciels-bpi.ca...
I perceived the introduction of `file()' as a nice cleanup in Python.
As a user, so did I. I like the cosistency of using file along with int, tuple, list, dict, type, (and did I leave out something), and all user classes as constructors of instances of themselves. I considered more as the action being performed. I'm opening something, in this case a file. And now I have an object which has been opened, I can perform operations on it, and when I'm done I close it.
But you pass a string to open. Are you opening a string? No. I might agree if there was some annotation on that string that said "I am a native platform filesystem path", but there isn't.
-bob -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2357 bytes Desc: not available Url : http://mail.python.org/pipermail/python-dev/attachments/20040709/42c9911b/smime.bin
- Previous message: [Python-Dev] Re: file() or open()?
- Next message: [Python-Dev] Re: Re: file() or open()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]