By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,941 Members | 1,789 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,941 IT Pros & Developers. It's quick & easy.

problems with using the Compiler module

P: n/a

I am wanting to create a simple code inspector and the Compiler module
seems to be a good starting point. However there seems to be either a
problem with the module, or with the way that I'm using it.

once I get the AST, I want to traverse the tree pulling out certain
information. For this I wanted to use node.getType() to deal with a
specific type of node correctly.

But all that node.getType() ever returns is None. Is this method
depreciated? If not then why will it only return None?

Also, does anyone know of any extensions to the Compiler module to simplify
certain actions, such as searching for all functions called within a

Thanks for any help
Stephen Emslie

mail2web - Check your email from the web at .

Jul 18 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.