[Python-Dev] ast branch pragmatics
Guido van Rossum
gvanrossum at gmail.com
Wed Jan 5 19:23:49 CET 2005
> I think it would be easier to create a new branch from the current
> head, integrate the small number of changed files from ast-branch, and
> work with that branch instead. The idea is that it's an end-run
> around doing an automatic CVS merge and relying on someone to manually
> merge the changes.
>
> At the same time, since there is a groundswell of support for
> finishing the AST work, I'd like to propose that we stop making
> compiler / bytecode changes until it is done. Every change to
> compile.c or the bytecode ends up creating a new incompatibilty that
> needs to be merged.
>
> If these two plans sound good, I'll get started on the new branch.
+1
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev
mailing list