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 ezio.melotti
Recipients Julian, docs@python, eric.araujo, ezio.melotti, rhettinger
Date 2011-11-21.12:06:15
SpamBayes Score 3.361004e-07
Marked as misclassified No
Message-id <>
There are usually two cases that lead me to check the code:
1) The documentation is incomplete, not clear, missing, or plain wrong;
2) I want to check how something is implemented, mostly just out of curiosity;

Regarding the first case, in theory the docs should be informative and correct enough to not require you to go and check the code.  If they aren't you can report issues and we can improve it.
The second case applies to pretty much any module.  Linking to the code might also expose some internal details that should be just ignored by the user.  The code in some modules is also pretty old and might be a "bad" example (because it doesn't use modern conventions).
Some of the modules you listed are actually packages, so that would require to link to several files.
Date User Action Args
2011-11-21 12:06:16ezio.melottisetrecipients: + ezio.melotti, rhettinger, eric.araujo, docs@python, Julian
2011-11-21 12:06:16ezio.melottisetmessageid: <>
2011-11-21 12:06:15ezio.melottilinkissue13437 messages
2011-11-21 12:06:15ezio.melotticreate