Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068970.html below:

[Python-Dev] AST structure and maintenance branches

• Previous message: [Python-Dev] Typo.pl scan of Python 2.5 source code
• Next message: [Python-Dev] AST structure and maintenance branches
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'd like to propose that the AST format returned by passing PyCF_ONLY_AST to 
compile() get the same guarantee in maintenance branches as the bytecode 
format - that is, unless it's absolutely necessary, we'll keep it the same. 
Otherwise anyone trying to write tools to manipulate the AST is in for a 
massive world of hurt.

Anyone have any problems with this, or can it be added to PEP 6?

Anthony

• Previous message: [Python-Dev] Typo.pl scan of Python 2.5 source code
• Next message: [Python-Dev] AST structure and maintenance branches
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4