You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Alexandro Colorado <jz...@oooes.org> on 2012/12/01 07:18:27 UTC
Re: [QA] Python version late for MacOS
On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir <ro...@apache.org> wrote:
> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer <aw...@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
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
Hello Tsutomu;
----- Original Message -----
> From: Tsutomu Uchino
>
> Hi,
>
> 2012/12/2, Pedro Giffuni <pf...@apache.org>:
>> FWIW;
>>
>> After updating Python to 2.7.3 I started working on updating
>> pyuno so that it works with Python3 and Python2. I didn't
>> finish and I don't really have much time for that lately but
>> I will be glad to point someone else in the right direction.
>>
> I modified pyuno to support Python 3.3 with new functions added on 3.3.
> But it does not support Python from 3.0 to 3.2.
> If someone interested in it:
> https://github.com/hanya/pyuno3
> I will make a patch and attach to issue if required.
>
I have been playing a bit with your patches but I have issues getting it
to compile with python 2.7.3.
I will take your offer, if it's still available, and if you provide patches
against trunk I will be glad to review and commit them as long as
they don't break the build.
Pedro.
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
Hi Alexandro;
----- Messaggio originale -----
> Da: Alexandro Colorado
...
>
> Just as a note, OOo allows the user to select their own JVM and other
> things such as classpath, and such on the Tools - Options - Java.
> Could something like this be enabled for Python3 or 2 or would it be as
> hard as porting the bridge?
>
pyuno needs to know the python version during compile time. This is
different in Java because bytecode is made to be portable.
I guess you could build pyuno2 and pyuno3 but you would need to have
both python versions available. I think hanya may be thinking of something
like that in his pyuno3 project:
https://github.com/hanya/pyuno3/
cheers,
Pedro.
Re: [QA] Python version late for MacOS
Posted by Alexandro Colorado <jz...@oooes.org>.
Just as a note, OOo allows the user to select their own JVM and other
things such as classpath, and such on the Tools - Options - Java.
Could something like this be enabled for Python3 or 2 or would it be as
hard as porting the bridge?
On Tue, Dec 18, 2012 at 3:53 PM, Pedro Giffuni <pf...@apache.org> wrote:
> Hello guys;
>
> Just a quick note that thanks to Tsutomu-san and some tweaking around the
> tree with the 2to3 python script we basically support Python 3 as a system
> version now. There may still be some issues to fix (especially with
> mailmerge)
> but it should work now.
>
> I still think we should use Python 2.7.3 by default in the tree and I don't
> plan to change that for AOO 4.x but it is really cool to have upgrade
> options.
>
> Please do exercise the default Python support and report any regression.
>
> Pedro.
>
>
> ----- Messaggio originale -----
>
>
> >
> >Thank you Tsutomu-san!
> >
> > I am currently busy with other stuff but I am aware of what's needed in
> > our pyuno layer so I will examine your code soon.
> >
> > Pedro.
> >
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://es.openoffice.org
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
Hello guys;
Just a quick note that thanks to Tsutomu-san and some tweaking around the
tree with the 2to3 python script we basically support Python 3 as a system
version now. There may still be some issues to fix (especially with mailmerge)
but it should work now.
I still think we should use Python 2.7.3 by default in the tree and I don't
plan to change that for AOO 4.x but it is really cool to have upgrade options.
Please do exercise the default Python support and report any regression.
Pedro.
----- Messaggio originale -----
>
>Thank you Tsutomu-san!
>
> I am currently busy with other stuff but I am aware of what's needed in
> our pyuno layer so I will examine your code soon.
>
> Pedro.
>
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
Thank you Tsutomu-san!
I am currently busy with other stuff but I am aware of what's needed in
our pyuno layer so I will examine your code soon.
Pedro.
----- Original Message -----
> From: Tsutomu Uchino
>
> Hi,
>
> 2012/12/2, Pedro Giffuni :
>> FWIW;
>>
>> After updating Python to 2.7.3 I started working on updating
>> pyuno so that it works with Python3 and Python2. I didn't
>> finish and I don't really have much time for that lately but
>> I will be glad to point someone else in the right direction.
>>
> I modified pyuno to support Python 3.3 with new functions added on 3.3.
> But it does not support Python from 3.0 to 3.2.
> If someone interested in it:
> https://github.com/hanya/pyuno3
> I will make a patch and attach to issue if required.
>
> -Tsutomu
>
>> Adding support for Python3 in pyuno is important and people
>> that make their own packages will need it but in general I would
>> advice against doing the update to 3.x by default now. Let others
>> deal with the migration issues first ;).
>>
>> Pedro.
>>
>>
>> ----- Original Message -----
>>>
>>> On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir wrote:
>>>
>>>> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer
>>> 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?
>>>>
>>>>
>>>> -Rob
>>>>
>>>> > -Andre
>>>> >
>>>>
>>
>
Re: [QA] Python version late for MacOS
Posted by Tsutomu Uchino <ha...@gmail.com>.
Hi,
2012/12/2, Pedro Giffuni <pf...@apache.org>:
> FWIW;
>
> After updating Python to 2.7.3 I started working on updating
> pyuno so that it works with Python3 and Python2. I didn't
> finish and I don't really have much time for that lately but
> I will be glad to point someone else in the right direction.
>
I modified pyuno to support Python 3.3 with new functions added on 3.3.
But it does not support Python from 3.0 to 3.2.
If someone interested in it:
https://github.com/hanya/pyuno3
I will make a patch and attach to issue if required.
-Tsutomu
> Adding support for Python3 in pyuno is important and people
> that make their own packages will need it but in general I would
> advice against doing the update to 3.x by default now. Let others
> deal with the migration issues first ;).
>
> Pedro.
>
>
> ----- Original Message -----
>>
>> On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir wrote:
>>
>>> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer
>> 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?
>>>
>>>
>>> -Rob
>>>
>>> > -Andre
>>> >
>>>
>
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
Hello;
Sorry for the delay answering.
>________________________________
> From: Alexandro Colorado
>On 12/1/12, Pedro Giffuni <pf...@apache.org> wrote:
>> FWIW;
>>
>> After updating Python to 2.7.3 I started working on updating
>> pyuno so that it works with Python3 and Python2. I didn't
>> finish and I don't really have much time for that lately but
>> I will be glad to point someone else in the right direction.
>
>Any logs on the modifications or issues for the migration?
>
A nice website for this is:
http://python3porting.com/
There is a 2to3 python script that helps a lot but you have to avoid
making changes that can break the build with Python 2.7.3.
The python part is under control. What requires most care now is
converting the C part of pyuno. Just try to use the system
python and set up the environment variables for python3 and
you will notice exactly what is missing.
When we decide to switch, the next step is updating the tarball
and making sure it builds on all supported platforms.
>
>
>> Adding support for Python3 in pyuno is important and people
>> that make their own packages will need it but in general I would
>> advice against doing the update to 3.x by default now. Let others
>> deal with the migration issues first ;).
>
>Crazy idea here, but can we componetize the pyuno bridge, and offer it
>as an extension using it's own virtualenv. That way Python3 could be
>enable or disabled?
>
>Having a pre-compiled pyuno3.so provided as a packaged could help
>users choose or prepare. However the extension would need to be smart
>enough to know the OS/Arquitecture/Version of the installed OO?
>
Can't help there, sorry.
Pedro.
Re: [QA] Python version late for MacOS
Posted by Alexandro Colorado <jz...@oooes.org>.
On 12/1/12, Pedro Giffuni <pf...@apache.org> wrote:
> FWIW;
>
> After updating Python to 2.7.3 I started working on updating
> pyuno so that it works with Python3 and Python2. I didn't
> finish and I don't really have much time for that lately but
> I will be glad to point someone else in the right direction.
Any logs on the modifications or issues for the migration?
> Adding support for Python3 in pyuno is important and people
> that make their own packages will need it but in general I would
> advice against doing the update to 3.x by default now. Let others
> deal with the migration issues first ;).
Crazy idea here, but can we componetize the pyuno bridge, and offer it
as an extension using it's own virtualenv. That way Python3 could be
enable or disabled?
Having a pre-compiled pyuno3.so provided as a packaged could help
users choose or prepare. However the extension would need to be smart
enough to know the OS/Arquitecture/Version of the installed OO?
>
> Pedro.
>
>
> ----- Original Message -----
>>
>> On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir wrote:
>>
>>> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer
>> 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?
>>>
>>>
>>> -Rob
>>>
>>> > -Andre
>>> >
>>>
>
--
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org
Re: [QA] Python version late for MacOS
Posted by Pedro Giffuni <pf...@apache.org>.
FWIW;
After updating Python to 2.7.3 I started working on updating
pyuno so that it works with Python3 and Python2. I didn't
finish and I don't really have much time for that lately but
I will be glad to point someone else in the right direction.
Adding support for Python3 in pyuno is important and people
that make their own packages will need it but in general I would
advice against doing the update to 3.x by default now. Let others
deal with the migration issues first ;).
Pedro.
----- Original Message -----
>
> On Fri, Nov 30, 2012 at 8:33 AM, Rob Weir wrote:
>
>> On Fri, Nov 30, 2012 at 7:11 AM, Andre Fischer
> 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?
>>
>>
>> -Rob
>>
>> > -Andre
>> >
>>