> I'm not talking about Twisted moving to 3.x (FWIW, I think the only > movement there so far is some patches for some -3 warnings). The > situation I'm describing is a project X that: > > (a) has 2.x-only dependencies, and > (b) would like to be as close as possible to 3.x (because they like > the new features and/or want to be as ready as possible to jump > when (a) is fixed).
This assumes that jumping to 3.x is easier if you are closer to it. Please trust me that this is not the case. >> No, it won't. It might be if people move to 2.8 *and* drop 2.5, but they >> likely won't. > > But this is my point. I think they would as an intermediate step to > jumping to 3.x (which also requires dropping 2.5, after all!), if for > some reason they cannot yet jump to 3.x, such as a 2.x-only dependency. No, and no. No: it's not an intermediate step, and no, supporting 3.x does *not* require dropping 2.5. Regards, Martin _______________________________________________ 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
