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.

Author terry.reedy
Recipients docs@python, eric.araujo, ezio.melotti, georg.brandl, terry.reedy
Date 2011-06-17.21:25:05
SpamBayes Score 9.667246e-10
Marked as misclassified No
Message-id <1308345906.05.0.881966267005.issue12298@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that all table entries should link to the entry in the same file.

dict() and set() also jump to CH. 4, in addition to memoryview and frozenset. Others all work properly.

The entries for classes should generally have a link to their section in '4. Built-in Types'. All do other than these:

range() definitely needs a forward reference to 4.6 sequence types 

bool() lacks forward references; it could have one to 4.2 Bool ops and 4.11.9 Bool values

object() -- no where to go.

slice() only has a reference to the glossary; it has no entry in Ch.4. "Slice objects have read-only data attributes start, stop and step which merely return the argument values (or their default). They have no other explicit functionality" is slightly wrong since there is the .indices method.

type(n,b,d) has no forward references as there is no where to go exactly
History
Date User Action Args
2011-06-17 21:25:06terry.reedysetrecipients: + terry.reedy, georg.brandl, ezio.melotti, eric.araujo, docs@python
2011-06-17 21:25:06terry.reedysetmessageid: <1308345906.05.0.881966267005.issue12298@psf.upfronthosting.co.za>
2011-06-17 21:25:05terry.reedylinkissue12298 messages
2011-06-17 21:25:05terry.reedycreate