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 Xezlec
Recipients Xezlec, docs@python, methane, r.david.murray
Date 2016-12-28.01:45:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482889558.28.0.0899697532357.issue29089@psf.upfronthosting.co.za>
In-reply-to
Content
> It's the tutorial.  Probably better to just leave it alone.  Precise understanding can come later.

But the problem isn't that it's imprecise.  It's flat-out wrong.  My opinion would be that it's always a bad idea to put wrong information in the documentation, especially when it's the first Google hit.  It can lead to all sorts of confusion and frustration (as it did for me).  Users are likely to assume documentation from any official source is the final word.

If precision is the problem, could it be reworded to be more vague?
History
Date User Action Args
2016-12-28 01:45:58Xezlecsetrecipients: + Xezlec, r.david.murray, methane, docs@python
2016-12-28 01:45:58Xezlecsetmessageid: <1482889558.28.0.0899697532357.issue29089@psf.upfronthosting.co.za>
2016-12-28 01:45:58Xezleclinkissue29089 messages
2016-12-28 01:45:57Xezleccreate