Message136145
| Author |
sheep |
| Recipients |
docs@python, ezio.melotti, georg.brandl, lukasz.langa, rhettinger, sheep, tim.golden |
| Date |
2011年05月17日.09:16:48 |
| SpamBayes Score |
2.1167358e-08 |
| Marked as misclassified |
No |
| Message-id |
<1305623810.06.0.242144878193.issue12086@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I am reporting this specifically because I just had two independent cases of people who submitted code that had almost all methods name-mangled (within 2 weeks), and who then pointed to that section of the tutorial as justification. I have a hard time convincing them that it is a bad idea, as I have to work against the official documentation here.
I agree that the language and library references should explain the mechanics behind the language in a neutral and empowering way. But I think that tutorial shouldn't tell people to write horrible code.
Perhaps it would suffice if the tutorial didn't call this "private methods"? A more descriptive and accurate section name, such as "name mangling" or "avoiding name clashes" could help a lot. |
|