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 dominic108
Recipients docs@python, dominic108, eric.smith, martin.panter, r.david.murray
Date 2017-04-01.22:16:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491084984.73.0.490497235367.issue29947@psf.upfronthosting.co.za>
In-reply-to
Content
The reason why I feel we should not make it immediately a documentation issue is that I don't know how a person working on documentation could proceed ahead without a clear go ahead signal from developers. In that sense,  having a documentation that says that the variable name does not reflect its intent seems tricky. It's very easy to change a variable name. It cannot possibly break the code, except for a collision, but they are easy to avoid.  If we don't have the interest of developers, not even for a simple renaming, I don't see a go ahead signal in this.
History
Date User Action Args
2017-04-01 22:16:24dominic108setrecipients: + dominic108, eric.smith, r.david.murray, docs@python, martin.panter
2017-04-01 22:16:24dominic108setmessageid: <1491084984.73.0.490497235367.issue29947@psf.upfronthosting.co.za>
2017-04-01 22:16:24dominic108linkissue29947 messages
2017-04-01 22:16:24dominic108create