On Thu, Mar 20, 2008 at 11:02 PM, Mike Meyer <[EMAIL PROTECTED]> wrote: > Fair enough. But doesn't 2.5->2.6 present the same problem? After all, > you can't start using 2.6 features until everyone is using it, right?
No, but you can start using 2.6 before everyone is using it, since 2.6 is backwards compatible with 2.5. So you write 2.5 code, and run it under 2.5 or 2.6. This is not possible with 3.0. You can't write 2.5 code and run it under 3.0. > Given that a simultaneous conversion is unrealistic, you clearly > expect to have some people running on 2.6 while others are running on > 2.5. Yes I can. > Why? Once you've got your web site working on 3.0, what's the point of > keeping the 2.6 web site around? Yes, you need to keep the 2.6 *code* > around, but that's a different issue, dealt with below. Yeah, you are right about that point, except for the compilation and the fact that you are debugging a different version of the code than the one you are writing, which of course is highly confusing, it is similar to having 2.5/2.6. The difference is that with 2.5/2.6 you develop for one, and then when that works, you make sure it works on the other. With 2.6/3.0 you have to develop both at once. You are right that you don't have to test them at once, though. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
