This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Docs for file() vs open()
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: rhettinger Nosy List: georg.brandl, rhettinger
Priority: normal Keywords: patch

Created on 2005-01-01 07:50 by georg.brandl, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
file-open-docs.diff georg.brandl, 2005-01-01 07:50 Patch
Messages (1)
msg47438 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-01-01 07:50
This is in reference to the thread on python-dev
starting 2004/07/07, subject "file() or open()?". Guido
stated there that one should use open() to open files:

"""Anyway, here's my future-proof distinction: use
open() as the factory function, and file for
type-testing."""

The docs, however, still convince the reader that
open() is retained for backwards compatibility and near
deprecation. This patch corrects the issue, mostly
using Guido's own new wording.
History
Date User Action Args
2022-04-11 14:56:08adminsetgithub: 41384
2005-01-01 07:50:52birkenfeldcreate