From: Jim B. <jb...@zy...> - 2010-01-06 05:22:19
|
Agreed, 2.5.2 is our most important short-term goal. We may also want to consider further 2.5.x releases too. Like 2.5.2 this would focus on improving Java integration and Jython performance. Longer term, supporting 2.7 puts us in the mainstream of core Python dev. In reviewing http://docs.python.org/dev/whatsnew/2.7.html, what stands out is that this is mostly a backport of 3.x functionality. (Some of this is pure Python too, so no extra work for us.) So we should go for 2.7 and skip a formal 2.6 release. - Jim On Tue, Jan 5, 2010 at 8:45 PM, Frank Wierzbicki <fwi...@gm...>wrote: > First I want to say that the short term target must be 2.5.2 and the > long term goal should be 3.x. Since the 2to3 tool for moving Python > code from 2.x to 3.x requires a minimum of 2.6 - we can't jump > straight to 3.x from 2.5.x > > With that out of the way.... > > Going for 2.6 means targeting a stable released CPython and sets us up > to go for 3.x a bit more quickly. Going for 2.7 means we get to > target the current development branch of CPython -- and possibly the > last 2.x we'd ever need to support. I hope to avoid doing both -- > whichever we do might be the last supported version of Jython 2.x. I > don't think we have the manpower to continue to support 2.5 (which I'd > like to see supported for at least a few years) and two other 2.x > releases. > > Thoughts? > > -Frank > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > -- Jim Baker jb...@zy... |