A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2001-August/017027.html below:

[Python-Dev] Re: AST mining (was Re: Direction of PyChecker)

[Python-Dev] Re: AST mining (was Re: Direction of PyChecker)Neal Norwitz neal@metaslash.com
Tue, 14 Aug 2001 11:13:32 -0400
David Goodger wrote:
> 
> >From the PyChecker AST discussion, it seems we may have a common goal. For

It seems that way.

> the Docstring Processing System, I am looking into gleaning information from
> the abstract syntax tree. From the working notes, under "Docstring
> Extractor":
> 
>     We need code that scans a parsed Python module, and returns an
>     ordered tree containing the names, docstrings (including
>     additional docstrings), and additional info (in parentheses below)
>     of all of the following objects:

>     - methods (+ formal parameters)
>     - functions (+ formal parameters)

Would you also want default parameter values?

PyChecker needs all of that, plus additional info.  So there is a lot
of overlap.

> I'd be very interested in pooling efforts to make this easier. I know almost
> nothing about ASTs now, but that could change in a hurry :-).

Pooling efforts would be good.  I also don't know anything about 
the ASTs/compiler, but am willing to work on it.

Neal



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