[Python-Dev] Policy for making changes to the AST (original) (raw)
Brett Cannon brett at python.org
Sun Apr 3 21:40:24 CEST 2011
- Previous message: [Python-Dev] Policy for making changes to the AST
- Next message: [Python-Dev] Policy for making changes to the AST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Apr 2, 2011 at 23:55, "Martin v. Löwis" <martin at 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 at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110403/5139debb/attachment.html>
- Previous message: [Python-Dev] Policy for making changes to the AST
- Next message: [Python-Dev] Policy for making changes to the AST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]