[ python-Bugs-1411674 ] "print statement" in libref index broken
SourceForge.net
noreply at sourceforge.net
Thu Apr 27 02:14:07 CEST 2006
Bugs item #1411674, was opened at 2006-01-21 14:50
Message generated for change (Settings changed) made by fdrake
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1411674&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.5
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Skip Montanaro (montanaro)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: "print statement" in libref index broken
Initial Comment:
The "print statement" entry in the libref index refers the user to
http://www.python.org/dev/doc/devel/lib/types.html#l2h-92
The source (libstdtypes.tex):
\ulink{\keyword{print} statement}{../ref/print.html}
suggests that the link should be to the reference manual. Something's
fishy. This was reported on comp.lang.python by
peter at monicol.co.uk. His report was against the current doc, but
the problem still exists in the development version.
Just passing it along...
----------------------------------------------------------------------
>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2006-04-26 20:14
Message:
Logged In: YES
user_id=3066
I think it's reasonable. It's about the fact that print
uses the str() function, so it's clearly about the print
statement. This information is good to have linked from the
index, I think.
No need to change anything.
----------------------------------------------------------------------
Comment By: Georg Brandl (birkenfeld)
Date: 2006-01-21 14:59
Message:
Logged In: YES
user_id=1188172
The output is okay. The \ulink you state does not add the
index entry, it's the \stindex one line above it.
But it's questionable whether this mention of print merits
an index entry. Fred?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1411674&group_id=5470
More information about the Python-bugs-list
mailing list