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 chris.jerdonek
Recipients BreamoreBoy, amirouche, bob.ippolito, chris.jerdonek, eric.araujo, ezio.melotti, flox, ggenellina, mark.dickinson, r.david.murray, rhettinger, serhiy.storchaka, techtonik
Date 2012-11-27.20:19:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354047550.89.0.486677282756.issue4945@psf.upfronthosting.co.za>
In-reply-to
Content
On the whole, the patch looks okay to me.  I think we should strive for correctness in the documentation where possible.

While keeping "True" would keep the forward implications correct and document the "preferred" value, there is often an implied assumption (which is sometimes stated) that the negation of the first term does not trigger or guarantee the behavior described in the second term.  It is that second implication that would be incorrect in some cases if "True" is kept (e.g. *check_circular* and *allow_nan*).

In cases where both "if True" and "if False" are explicitly stated, keeping "True" and "False" would mean not documenting certain cases.
History
Date User Action Args
2012-11-27 20:19:10chris.jerdoneksetrecipients: + chris.jerdonek, rhettinger, bob.ippolito, mark.dickinson, ggenellina, techtonik, ezio.melotti, eric.araujo, r.david.murray, flox, BreamoreBoy, amirouche, serhiy.storchaka
2012-11-27 20:19:10chris.jerdoneksetmessageid: <1354047550.89.0.486677282756.issue4945@psf.upfronthosting.co.za>
2012-11-27 20:19:10chris.jerdoneklinkissue4945 messages
2012-11-27 20:19:10chris.jerdonekcreate