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 r.david.murray
Recipients BreamoreBoy, amirouche, bob.ippolito, chris.jerdonek, eric.araujo, ezio.melotti, flox, ggenellina, mark.dickinson, r.david.murray, rhettinger, serhiy.storchaka, techtonik, zearin
Date 2013-01-29.19:26:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359487583.46.0.6244639959.issue4945@psf.upfronthosting.co.za>
In-reply-to
Content
I would be very careful trying to reason by analogy there.  ==, is, and javascripts === are rather different in detail, from what I understand.  Nor do I see what javascript has to do with this issue :)

As far as the remaining documentation issue here, IMO to follow the convention used most often in the docs (and docstrings), the text in Chris' example should read:

   If *allow_nan* is true

That is, drop the code markup and capitalization to indicate that any true value is accepted.  A naive user will use True, a non-naive user will understand the implication.  I know Ezio doesn't think this is worthwhile, but I disagree :)
History
Date User Action Args
2013-01-29 19:26:23r.david.murraysetrecipients: + r.david.murray, rhettinger, bob.ippolito, mark.dickinson, ggenellina, techtonik, ezio.melotti, eric.araujo, flox, chris.jerdonek, BreamoreBoy, amirouche, serhiy.storchaka, zearin
2013-01-29 19:26:23r.david.murraysetmessageid: <1359487583.46.0.6244639959.issue4945@psf.upfronthosting.co.za>
2013-01-29 19:26:23r.david.murraylinkissue4945 messages
2013-01-29 19:26:23r.david.murraycreate