GvR> For tools like PyChecker, a higher level is more appropriate: give
GvR> it an abstract syntax tree that can answer questions related to the
GvR> symbol table, so that you can tell for example whether 'x = y'
GvR> assigns a local to a global or vice versa -- and if a local is
GvR> involved, in which function it is defined.
Jeremy> I'm not sure how much time I can make for it in the 2.2 release
Jeremy> schedule, but I think a high-level source analysis module would
Jeremy> be a valuable addition to the compiler package. We've got
Jeremy> pychecker and pydoc as to drive the requirements. Do you think
Jeremy> it's worth making time for in the 2.2 release schedule?
I don't think so. Designing features to suit the needs of just two tools
may result in a module that's suited for them. Pydoc and pychecker work
now. I suggest working on such a module for 2.3 instead, where you'll have
a fair bit of time to properly analyze the requirements.
Skip
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