Issue 922964: file built-in object is after file() function (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/40077

classification

process

Created on 2004-03-25 08:18 by nerby, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg20311 - (view)	Author: Francesco Ricciardi (nerby)	Date: 2004-03-25 08:18
In section 2.1 of the HTML and PDF-A4 library references (so supposedly in all lib references), in the description of the file() function, it says that "Return a new file object (described earlier under Built-in Types)", but the Built-in Types section is later not earlier.
msg20312 - (view)	Author: Raymond Hettinger (rhettinger) *	Date: 2004-03-25 08:28
Logged In: YES user_id=80475 Forward references are only problematic in the tutorial. The rest of the docs tend to be used in a random access fashion rather than sequentially. That's a good thing because forward references are everywhere.
msg20313 - (view)	Author: Michael Hudson (mwh)	Date: 2004-03-29 17:57
Logged In: YES user_id=6656 That's not what he's complaining about, though. Seems to me that just removing the 'earlier' would suffice.
msg20314 - (view)	Author: Tim Peters (tim.peters) *	Date: 2004-04-05 23:55
Logged In: YES user_id=31435 Assigned to Fred. The LaTeX currently has """ Return a new file object (described in section~\ref{bltin-file-objects}, ``\ulink{File Objects}{bltin-file-objects.html}''). """ so I expect this should just be closed, as already fixed.
msg20315 - (view)	Author: Fred Drake (fdrake)	Date: 2004-05-06 04:00
Logged In: YES user_id=3066 Closing as out-of-date; as Tim notes, the CVS version of the documentation has already been made direction-agnostic.