<div class="gmail_quote">On Tue, Nov 3, 2009 at 9:37 AM, "Martin v. Löwis" <span dir="ltr"><<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
(and no, adding things like nonlocal to 2.7 doesn't making porting of<br>
a real application or library any easier, since the existing application<br>
or library simply doesn't use that keyword. In fact, no change to 2.x<br>
can reasonably simplify porting - only changes to 3.x might - except<br>
for changes to 2to3, which can simplify porting a lot. But 2to3 should<br>
be run under 3.x, IMO.)<br></blockquote><div><br></div><div>I agree that adding these features doesn't really help much for people that are porting from 2.x to 3.x. However, I can see it being useful for package developers who want to support both 3.x and 2.x. The more these two versions have in common the easier it will be to support them both. Obviously, this means the package might not work with 2.6 and earlier. But some users out there might be in some situation where they cannot upgrade to 3.x but can jump from 2.4/5/6 to 2.7.</div>
<div><br></div><div>-Farshid</div></div>