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 serhiy.storchaka
Recipients James.Salt, docs@python, eric.araujo, larry, petere, sandro.tosi, serhiy.storchaka
Date 2012-09-28.18:26:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348856783.21.0.601192065654.issue16026@psf.upfronthosting.co.za>
In-reply-to
Content
Changing the documentation is changing the specification, it has the higher bar than changing the implementation. It can break the alternative implementations.

This is unlikely to break somebody's existing code, because the one who used the argument as a keyword argument should have paid attention to the discrepancy of the documentation. But fixing the name, we will be difficult to change it in the future (to eliminate inconsistency).

I believe this change is too serious for bugfix. This is the case when never is better than *right* now.
History
Date User Action Args
2012-09-28 18:26:23serhiy.storchakasetrecipients: + serhiy.storchaka, larry, eric.araujo, petere, sandro.tosi, docs@python, James.Salt
2012-09-28 18:26:23serhiy.storchakasetmessageid: <1348856783.21.0.601192065654.issue16026@psf.upfronthosting.co.za>
2012-09-28 18:26:23serhiy.storchakalinkissue16026 messages
2012-09-28 18:26:23serhiy.storchakacreate