Message291005
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. |
|
Date |
User |
Action |
Args |
2017-04-01 22:16:24 | dominic108 | set | recipients:
+ dominic108, eric.smith, r.david.murray, docs@python, martin.panter |
2017-04-01 22:16:24 | dominic108 | set | messageid: <1491084984.73.0.490497235367.issue29947@psf.upfronthosting.co.za> |
2017-04-01 22:16:24 | dominic108 | link | issue29947 messages |
2017-04-01 22:16:24 | dominic108 | create | |
|