On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir <robw...@apache.org> wrote:
> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer <awf....@gmail.com> wrote: > > On 30.11.2012 12:02, FR web forum wrote: > >>> > >>> In trunk we currently have version 2.7.3. Would that be OK? > >> > >> Python 2.7.3 is in end of life. > >> > >> It will be better to directly include Python 3.3. > >> Compatibility for extensions will be more easy with future LibO 4 that > use > >> already this version. > > > > > > I thought that 2.x is incompatible from 3.x. Would existing extensions > still > > work with 3.3? > > > > Moving to 3.x would be an incompatible change. But 2.7.x is on > "extended maintenance" but no new features are being done there. > > So the future is certainly with 3.x. But we would need to communicate > very carefully with extension authors if we want to make this move. > We want to avoid this: > > 1) AOO 4.0 comes out with broken extensions and unhappy users > > 2) Extension authors have insufficient time to test with Python 3.x > support, leading to 1 > > 3) Extension authors are not aware that we are switching to Python > 3.x, leading to 1 > > So if we want to do this we would need to notify extension authors > ASAP and give them a way to test their extensions with Python 3.x. So > maybe integrate the new Python early and have a developer preview > version that they can test with? > Any chances to use virtualenv to have a fallback mode? What would need to be done? How non-trivial would that be? > > -Rob > > > -Andre > > > -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org
