[Docstring-develop] pydps - function signatures and Tools/compiler questions

[Tony J I. (Tibs) <to...@ls...>]

It's still

      	http://www.tibsnjoan.co.uk/reST/pydps.tgz

I've started adding support for function signatures. This has meant
working on producing representations for the RHS of assignments, which
is partially completed (it does, for instance, list comprehensions, but
not basic arithmetic). See my other message on the Doc-SIG as such today
(Re: [Doc-SIG] DPS DTDs) for an example of what it handles.

Jeremy - this means that I'm getting a *much* better understanding of
some of the nodes in the compiler tree. I realise that the table in

	http://www.python.org/~jeremy/compiler/module-compiler.ast.html

is generated from LaTeX source, presumably that at


http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/To
ols/compiler/doc/asttable.tex

(well, when I browse it). I'm willing to update that, in whatever form
is useful, with more information about what each "entry" is. What's the
best way for me to do that, so far as you're concerned? (taking a copy
of the LaTeX and working on it would be OK by me).

Two other questions:

1. Is there a possibility that the compiler module might get shifted
from Tools into the standard library? It seems rather too useful to be
stuck "in the hinterlands".

2. Should the various representation functions I'm working on eventually
be merged in as methods on the compiler nodes? I'm a bit chary of having
code outwith the compiler module that has to know details about a good
number of the nodes inside (e.g., the problems if a new class gets
added). On the other hand, cruft that (maybe) no-one else would want
would be a bad thing...

Tibs

--
Tony J Ibbs (Tibs)      http://www.tibsnjoan.co.uk/
You said "run as root" and "securely" in the same sentence relating to
CGI. You're funny! -- Ignacio Vazquez-Abrams, on the Python list
My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)