Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-July/045962.html below:

[Python-Dev] file() or open()?

• Previous message: [Python-Dev] file() or open()?
• Next message: [Python-Dev] file() or open()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Guido van Rossum wrote:

[SNIP]
> In the future, I could see
> open() become a factory function again that could return an instance
> of a different class depending on the mode argument, the default
> encoding for files, or who knows what; but file will always remain a
> class.

How is this case different from the whole unicode.encode thread and the 
worry of having different types of objects returned based on the 
argument?  I would assume that any objects returned would follow the 
file interface roughly.

-Brett

• Previous message: [Python-Dev] file() or open()?
• Next message: [Python-Dev] file() or open()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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