On Tue, 2004-07-06 at 23:08, Guido van Rossum wrote: > > I have always used open() myself. does this mean we should continue > > to use open()? > > IMO, yes. My posting was intended to draw attention to the fact that > apparently some developers think differently. I'm hoping to revert > their opinions unless there's a really good reason to switch to > file(). +1 from me. We've been using "open()" to mean open for about as long as there have been Python programs, right? I don't see any value to changing the name at this point, and I see harm in having inconsistent use of open vs. file in the standard library. Jeremy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4