Jeremy Hylton <[EMAIL PROTECTED]> writes: > The existing ast-branch mostly works, but it does not include most of > the new features of Python 2.4. There is a substantial integration > effort, perhaps easy for someone who does a lot of CVS branch merges. > (In particular, the head has already been merged to this branch once.) > > 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.
Hm, I saw this after making my previous post. Well, you can see from that post that it's a bit of work, but not overwhelming. You have a better feel for how much change was made on ast-branch and how complete the previous merge was. So, you decide: if you want me to do the merge, I can. But ast-branch-2 sounds OK, also. -- KBK _______________________________________________ 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/archive%40mail-archive.com
