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 methane
Recipients Xezlec, docs@python, methane, r.david.murray
Date 2016-12-28.02:41:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482892909.52.0.93574475294.issue29089@psf.upfronthosting.co.za>
In-reply-to
Content
> If precision is the problem, could it be reworded to be more vague?

"can be any immutable" seems vague enough to me.  It doesn't say "cannot be any mutable type.".

>  Users are likely to assume documentation from any official source is the final word.

But tutorial should use less words as possible.  This section is before introducing "class" statement.  Only strings, numbers, list and set are introduced before section.

I feel assuming early part of tutorial as final word bad practice.
History
Date User Action Args
2016-12-28 02:41:49methanesetrecipients: + methane, r.david.murray, docs@python, Xezlec
2016-12-28 02:41:49methanesetmessageid: <1482892909.52.0.93574475294.issue29089@psf.upfronthosting.co.za>
2016-12-28 02:41:49methanelinkissue29089 messages
2016-12-28 02:41:49methanecreate