Hi Sanjay, * sanjay nadkarni (Laptop) (Sanjay.Nadkarni at Sun.COM) wrote: > Joe, > I am looking at Glenn's initial email which indicated that the > webrev did not include Python 2.6 changes. I am assuming that all > the updated webrevs are still not in sync with Python 2.6. If this > is not true then there are a few references to to Python 2.4 and > also some merge errors.
The bulk of the webrev does not include Python 2.6 changes as we weren't merged with those changes. The one specific case where that's not true is for im_pop.py (previously known as DC_tm.py). I've got a merge of VMC with python 2.6 workspace which I'm regression testing right now. I don't plan to send out another webrev based on this workspace since merge changes shouldn't really need reviewing. Does this address any concerns you had? Thanks, -- Glenn
