[Python-Dev] Policy for making changes to the AST (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Mon Apr 4 19:38: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 04/04/2011 18:05, fwierzbicki at gmail.com wrote:
As a re-implementor of ast.py that tries to be node for node compatible, I'm fine with #1 but would really like to have tests that will fail in testast.py to alert me!
A lot of tools that work with Python source code use ast - so even though other implementations may not use the same ast "under the hood" they will probably at least want to provide a compatible implementation. IronPython is in that boat too (although I don't know if we have a compatible implementation yet - we certainly feel like we should have one).
Michael
-Frank
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/fuzzyman%40voidspace.org.uk
-- http://www.voidspace.org.uk/
May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.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 ]