> 1. Do nothing. This will break code that currently uses AST, but doesn't add
> any complexity to cpython.

I'm in favor of this approach as well. Notice that there is
ast.__version__ precisely so that applications can support multiple AST
versions.

As someone who actually does use the AST (http://code.google.com/p/mnfy/), I am in favour of #1 thanks to ast.__version__. I actually have a version check in my code to make sure that if a change occurs my tests fail and I know I need to update things.
">

(original) (raw)



On Sat, Apr 2, 2011 at 23:55, "Martin v. Löwis" <martin@v.loewis.de> wrote:

> 1\. Do nothing. This will break code that currently uses AST, but doesn't add
> any complexity to cpython.

I'm in favor of this approach as well. Notice that there is
ast.\_\_version\_\_ precisely so that applications can support multiple AST
versions.

As someone who actually does use the AST (http://code.google.com/p/mnfy/), I am in favour of #1 thanks to ast.\_\_version\_\_. I actually have a version check in my code to make sure that if a change occurs my tests fail and I know I need to update things.

Regards,
Martin
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org