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 r.david.murray
Recipients docs@python, eric.araujo, georg.brandl, ifreecarve, r.david.murray, rhettinger, sbt
Date 2017-07-11.17:44:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499795069.7.0.0147743855031.issue10438@psf.upfronthosting.co.za>
In-reply-to
Content
Given a choice between catering for Python programmers and catering for Java/C++ programmers, the Python docs obviously ought to chose to cater to Python programmers.  To a python programmer, calling C.f() is intuitive.

I would myself definitely *not* encourage the __class__.f() idiom.

Maybe we should just drop the reference to Java and C++ static methods.
History
Date User Action Args
2017-07-11 17:44:29r.david.murraysetrecipients: + r.david.murray, georg.brandl, rhettinger, eric.araujo, docs@python, ifreecarve, sbt
2017-07-11 17:44:29r.david.murraysetmessageid: <1499795069.7.0.0147743855031.issue10438@psf.upfronthosting.co.za>
2017-07-11 17:44:29r.david.murraylinkissue10438 messages
2017-07-11 17:44:29r.david.murraycreate