The parser module exports each function and type twice, once with "AST" in the name, once with "ST". Since "AST" now has a different meaning for Python code compilation, I propose to deprecate the "ast" variants in 2.6 and remove them in Python 3000.
(Also, all keyword arguments are called "ast", that cannot change in 2.6 but should in 3.0.)
I'm at the moment changing the documentation of parser to only refer to the "st" variants anymore.
Georg
On Sat, Jun 7, 2008 at 3:13 PM, Georg Brandl g.brandl@gmx.net wrote:
The parser module exports each function and type twice, once with "AST" in the name, once with "ST". Since "AST" now has a different meaning for Python code compilation, I propose to deprecate the "ast" variants in 2.6 and remove them in Python 3000.
+1 This personally has confused me!
(Also, all keyword arguments are called "ast", that cannot change in 2.6 but should in 3.0.)
I'm at the moment changing the documentation of parser to only refer to the "st" variants anymore.
Georg
+1 as well.
On Mon, Jul 21, 2008 at 7:47 AM, Benjamin Peterson musiccomposition@gmail.com wrote:
On Sat, Jun 7, 2008 at 3:13 PM, Georg Brandl g.brandl@gmx.net wrote:
The parser module exports each function and type twice, once with "AST" in the name, once with "ST". Since "AST" now has a different meaning for Python code compilation, I propose to deprecate the "ast" variants in 2.6 and remove them in Python 3000.
+1 This personally has confused me!
(Also, all keyword arguments are called "ast", that cannot change in 2.6 but should in 3.0.)
I'm at the moment changing the documentation of parser to only refer to the "st" variants anymore.
-
Benjamin Peterson -
Georg Brandl -
Guido van Rossum