"kasper b. graversen" <kbg at kadnet.dk> wrote in message news:200310101811370393.020A912A at lisbeth.kadnet.dom... At least your first two questions are about usage rather than development and would be better directed to comp.lang.python (or g.c.p.general) In the meanwhile... >each object. So far it has been fun playing with python, but I ponder why it is >only possible to introduce functions and not methods to object instances? 1. Methods are functions attached to classes as attributes. 2. The need for instance-specific 'methods' is rare. 3. Rare needs are covered by explicitly passing the instance as an arg: person.role(person, *args) > I am also wondering if it is possible to change the parsed code at compile > time by gaining access to the AST See compiler module/package and its AST walker. >Finally, one of the most difficult things of moving from Java to python is the >lack of checking done by the compiler ;) Here are two things I really miss >which if would like the future versions of the compiler to support: The current interpreter checks only for syntactic correctness and deprecated usages (to issue warnings). This is unlikely to change soon. Enforcing coding standards is more the province of PyChecker and PyLint. If neither have the checks you want, give both authors your suggestions. Terry J. Reedy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4