You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pedro Giffuni <pf...@apache.org> on 2020/01/02 02:30:03 UTC
Update to python-2.17
Hello AOO devs and best wishes for the New Year!
Well ... time has passed and Python 2 is now deprecated!
I have a patch here to update AOO 4.2's version of Python to the latest
(perhaps last) release in that line:
http://people.apache.org/~pfg/patches/patch-python-2.17.diff
This is a remake of the previous update that I had made for
cpython-2.16, but which no one tested ! I currently lack an AOO setup
with git so please someone else will have to test and commit.
On the near term, we really should update to Python 3, but that will be
challenging for the build system since it requires a newer version of
the MS compiler.
Building with an external python is also currently broken for python
versions >= 3.6.
Regards,
Pedro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Everything seems to work.
Thanks again!
Regards,
Matthias
Am 10.01.20 um 23:18 schrieb Matthias Seidel:
> Hi Pedro,
>
> Am 10.01.20 um 21:17 schrieb Pedro Giffuni:
>> On 2020-01-10 14:53, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Am 10.01.20 um 20:50 schrieb Pedro Giffuni:
>>>> On 2020-01-10 13:24, Matthias Seidel wrote:
>>>>> Hi Pedro,
>>>>>
>>>>> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>>>>>> Hi again;
>>>>>>
>>>>>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>>>>>> Hi Pedro,
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Unfortunately the build process just stops at some point (on Windows),
>>>>>>> no error codes I could give you.
>>>>>> The problems are usually related to getting the patches applied
>>>>>> correctly. There can be no hunks or mismatches.
>>>>>>
>>>>>> I tested them one by one and they should be OK now. Same place:
>>>>>>
>>>>>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>> When trying to apply this patch to trunk I get:
>>>>>
>>>>> **** malformed patch at line 2048: Index:
>>>>> main/python/python-2.7.15-msvs9.patch
>>>>>
>>>>> (It would be nice if you could create a Pull Request on GitHub)
>>>> Indeed that patch causes issues due to Windows LF characters. I
>>>> overruled the issue in git and sent the Pull Request:
>>>>
>>>> https://github.com/apache/openoffice/pull/23
>>> Thanks!
>>>
>>> What revision is this patch based on?
>>> I see a lot of commits that are already in trunk for longer time...
>>> (However, they should be ignored when merging?)
>> It's straight from recent git clone but I applied the changes manually.
>> Some crap crept into external_dps.lst but I cleaned them up with
>> successive commits.
>>
>> Do feel free to ignore any irrelevant change that might have crept in.
> I am now building with your latest changes.
>
> If everything goes well I will merge the PR tomorrow.
>
> Regards,
>
> Matthias
>
>> Pedro.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Am 10.01.20 um 21:17 schrieb Pedro Giffuni:
> On 2020-01-10 14:53, Matthias Seidel wrote:
>> Hi Pedro,
>>
>> Am 10.01.20 um 20:50 schrieb Pedro Giffuni:
>>> On 2020-01-10 13:24, Matthias Seidel wrote:
>>>> Hi Pedro,
>>>>
>>>> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>>>>> Hi again;
>>>>>
>>>>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>>>>> Hi Pedro,
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Unfortunately the build process just stops at some point (on Windows),
>>>>>> no error codes I could give you.
>>>>> The problems are usually related to getting the patches applied
>>>>> correctly. There can be no hunks or mismatches.
>>>>>
>>>>> I tested them one by one and they should be OK now. Same place:
>>>>>
>>>>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>> When trying to apply this patch to trunk I get:
>>>>
>>>> **** malformed patch at line 2048: Index:
>>>> main/python/python-2.7.15-msvs9.patch
>>>>
>>>> (It would be nice if you could create a Pull Request on GitHub)
>>> Indeed that patch causes issues due to Windows LF characters. I
>>> overruled the issue in git and sent the Pull Request:
>>>
>>> https://github.com/apache/openoffice/pull/23
>> Thanks!
>>
>> What revision is this patch based on?
>> I see a lot of commits that are already in trunk for longer time...
>> (However, they should be ignored when merging?)
> It's straight from recent git clone but I applied the changes manually.
> Some crap crept into external_dps.lst but I cleaned them up with
> successive commits.
>
> Do feel free to ignore any irrelevant change that might have crept in.
I am now building with your latest changes.
If everything goes well I will merge the PR tomorrow.
Regards,
Matthias
>
> Pedro.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Update to python-2.17
Posted by Pedro Giffuni <pf...@apache.org>.
On 2020-01-10 14:53, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 20:50 schrieb Pedro Giffuni:
>> On 2020-01-10 13:24, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>>>> Hi again;
>>>>
>>>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>>>> Hi Pedro,
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Unfortunately the build process just stops at some point (on Windows),
>>>>> no error codes I could give you.
>>>> The problems are usually related to getting the patches applied
>>>> correctly. There can be no hunks or mismatches.
>>>>
>>>> I tested them one by one and they should be OK now. Same place:
>>>>
>>>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>> When trying to apply this patch to trunk I get:
>>>
>>> **** malformed patch at line 2048: Index:
>>> main/python/python-2.7.15-msvs9.patch
>>>
>>> (It would be nice if you could create a Pull Request on GitHub)
>> Indeed that patch causes issues due to Windows LF characters. I
>> overruled the issue in git and sent the Pull Request:
>>
>> https://github.com/apache/openoffice/pull/23
> Thanks!
>
> What revision is this patch based on?
> I see a lot of commits that are already in trunk for longer time...
> (However, they should be ignored when merging?)
It's straight from recent git clone but I applied the changes manually.
Some crap crept into external_dps.lst but I cleaned them up with
successive commits.
Do feel free to ignore any irrelevant change that might have crept in.
Pedro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Am 10.01.20 um 20:50 schrieb Pedro Giffuni:
> On 2020-01-10 13:24, Matthias Seidel wrote:
>> Hi Pedro,
>>
>> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>>> Hi again;
>>>
>>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>>> Hi Pedro,
>>>>
>>>> Thanks!
>>>>
>>>> Unfortunately the build process just stops at some point (on Windows),
>>>> no error codes I could give you.
>>> The problems are usually related to getting the patches applied
>>> correctly. There can be no hunks or mismatches.
>>>
>>> I tested them one by one and they should be OK now. Same place:
>>>
>>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
>> When trying to apply this patch to trunk I get:
>>
>> **** malformed patch at line 2048: Index:
>> main/python/python-2.7.15-msvs9.patch
>>
>> (It would be nice if you could create a Pull Request on GitHub)
> Indeed that patch causes issues due to Windows LF characters. I
> overruled the issue in git and sent the Pull Request:
>
> https://github.com/apache/openoffice/pull/23
Thanks!
What revision is this patch based on?
I see a lot of commits that are already in trunk for longer time...
(However, they should be ignored when merging?)
Regards,
Matthias
>
> Enjoy!
>
> Pedro.
>
>
Re: Update to python-2.17
Posted by Pedro Giffuni <pf...@apache.org>.
On 2020-01-10 13:24, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>> Hi again;
>>
>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Thanks!
>>>
>>> Unfortunately the build process just stops at some point (on Windows),
>>> no error codes I could give you.
>> The problems are usually related to getting the patches applied
>> correctly. There can be no hunks or mismatches.
>>
>> I tested them one by one and they should be OK now. Same place:
>>
>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
> When trying to apply this patch to trunk I get:
>
> **** malformed patch at line 2048: Index:
> main/python/python-2.7.15-msvs9.patch
>
> (It would be nice if you could create a Pull Request on GitHub)
Indeed that patch causes issues due to Windows LF characters. I
overruled the issue in git and sent the Pull Request:
https://github.com/apache/openoffice/pull/23
Enjoy!
Pedro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Pedro Giffuni <pf...@apache.org>.
On 2020-01-10 13:24, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>> Hi again;
>>
>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Thanks!
>>>
>>> Unfortunately the build process just stops at some point (on Windows),
>>> no error codes I could give you.
>> The problems are usually related to getting the patches applied
>> correctly. There can be no hunks or mismatches.
>>
>> I tested them one by one and they should be OK now. Same place:
>>
>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
> When trying to apply this patch to trunk I get:
>
> **** malformed patch at line 2048: Index:
> main/python/python-2.7.15-msvs9.patch
This shouldn't happen because all -2.7.15 are removed in the patch and
replaced with 2.7.17 versions.
% ls python
makefile.mk
prj
python-2.7.17-msvs9-dir.patch
python-2.7.17-msvs9-no-host-python.patch
python-2.7.17-msvs9-python-path.patch
python-2.7.17-msvs9-subsystem.patch
python-2.7.17-msvs9-win64-target.patch
python-2.7.17-msvs9-win64.patch
python-2.7.17-msvs9.patch
python-2.7.17-nohardlink.patch
python-2.7.17-sysbase.patch
python-freebsd.patch
python-md5.patch
python-solaris.patch
python-solver-before-std.patch
python-ssl.patch
pyversion.mk
pyversion_dmake.mk
FWIW, I used "svn diff --patch-compatible", to generate the patch.
> (It would be nice if you could create a Pull Request on GitHub)
This would indeed by much easier for me. I'll do that!
Pedro.
> Regards,
>
> Matthias
>
>>> According to https://www.python.org/downloads/release/python-2717/ this
>>> is the "penultimate" release, so maybe there will be a final 2.7.18?
>> Yes, there will be a final release in a couple of months, but most linux
>> distributions (and FreeBSD) are already deprecating py27 and anything
>> that depends on it.
>>
>> Thanks for your patience!
>>
>> Pedro.
>>
>>> Regards,
>>>
>>> Matthias
>>>
>>> Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
>>>> Hi Matthias;
>>>>
>>>> Sorry about that. I could've tested better the patch. I will fix the
>>>> obvious issues and will let you guys know.
>>>>
>>>>
>>>> Pedro.
>>>>
>>>> ps. It may take me a while though, I am getting busy very fast :(
>>>>
>>>> On 2020-01-01 21:30, Pedro Giffuni wrote:
>>>>> Hello AOO devs and best wishes for the New Year!
>>>>>
>>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>>
>>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>>> (perhaps last) release in that line:
>>>>>
>>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>>
>>>>> This is a remake of the previous update that I had made for
>>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>>> with git so please someone else will have to test and commit.
>>>>>
>>>>> On the near term, we really should update to Python 3, but that will be
>>>>> challenging for the build system since it requires a newer version of
>>>>> the MS compiler.
>>>>>
>>>>> Building with an external python is also currently broken for python
>>>>> versions >= 3.6.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Pedro.
>>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
> Hi again;
>
> On 2020-01-04 05:16, Matthias Seidel wrote:
>> Hi Pedro,
>>
>> Thanks!
>>
>> Unfortunately the build process just stops at some point (on Windows),
>> no error codes I could give you.
> The problems are usually related to getting the patches applied
> correctly. There can be no hunks or mismatches.
>
> I tested them one by one and they should be OK now. Same place:
>
> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
When trying to apply this patch to trunk I get:
**** malformed patch at line 2048: Index:
main/python/python-2.7.15-msvs9.patch
(It would be nice if you could create a Pull Request on GitHub)
Regards,
Matthias
>
>> According to https://www.python.org/downloads/release/python-2717/ this
>> is the "penultimate" release, so maybe there will be a final 2.7.18?
> Yes, there will be a final release in a couple of months, but most linux
> distributions (and FreeBSD) are already deprecating py27 and anything
> that depends on it.
>
> Thanks for your patience!
>
> Pedro.
>
>> Regards,
>>
>> Matthias
>>
>> Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
>>> Hi Matthias;
>>>
>>> Sorry about that. I could've tested better the patch. I will fix the
>>> obvious issues and will let you guys know.
>>>
>>>
>>> Pedro.
>>>
>>> ps. It may take me a while though, I am getting busy very fast :(
>>>
>>> On 2020-01-01 21:30, Pedro Giffuni wrote:
>>>> Hello AOO devs and best wishes for the New Year!
>>>>
>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>
>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>> (perhaps last) release in that line:
>>>>
>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>
>>>> This is a remake of the previous update that I had made for
>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>> with git so please someone else will have to test and commit.
>>>>
>>>> On the near term, we really should update to Python 3, but that will be
>>>> challenging for the build system since it requires a newer version of
>>>> the MS compiler.
>>>>
>>>> Building with an external python is also currently broken for python
>>>> versions >= 3.6.
>>>>
>>>> Regards,
>>>>
>>>> Pedro.
>>>>
Re: Update to python-2.17
Posted by Pedro Giffuni <pf...@apache.org>.
Hi again;
On 2020-01-04 05:16, Matthias Seidel wrote:
> Hi Pedro,
>
> Thanks!
>
> Unfortunately the build process just stops at some point (on Windows),
> no error codes I could give you.
The problems are usually related to getting the patches applied
correctly. There can be no hunks or mismatches.
I tested them one by one and they should be OK now. Same place:
https://people.apache.org/~pfg/patches/patch-python-2.17.diff
> According to https://www.python.org/downloads/release/python-2717/ this
> is the "penultimate" release, so maybe there will be a final 2.7.18?
Yes, there will be a final release in a couple of months, but most linux
distributions (and FreeBSD) are already deprecating py27 and anything
that depends on it.
Thanks for your patience!
Pedro.
> Regards,
>
> Matthias
>
> Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
>> Hi Matthias;
>>
>> Sorry about that. I could've tested better the patch. I will fix the
>> obvious issues and will let you guys know.
>>
>>
>> Pedro.
>>
>> ps. It may take me a while though, I am getting busy very fast :(
>>
>> On 2020-01-01 21:30, Pedro Giffuni wrote:
>>> Hello AOO devs and best wishes for the New Year!
>>>
>>> Well ... time has passed and Python 2 is now deprecated!
>>>
>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>> (perhaps last) release in that line:
>>>
>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>
>>> This is a remake of the previous update that I had made for
>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>> with git so please someone else will have to test and commit.
>>>
>>> On the near term, we really should update to Python 3, but that will be
>>> challenging for the build system since it requires a newer version of
>>> the MS compiler.
>>>
>>> Building with an external python is also currently broken for python
>>> versions >= 3.6.
>>>
>>> Regards,
>>>
>>> Pedro.
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Thanks!
Unfortunately the build process just stops at some point (on Windows),
no error codes I could give you.
According to https://www.python.org/downloads/release/python-2717/ this
is the "penultimate" release, so maybe there will be a final 2.7.18?
Regards,
Matthias
Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
> Hi Matthias;
>
> Sorry about that. I could've tested better the patch. I will fix the
> obvious issues and will let you guys know.
>
>
> Pedro.
>
> ps. It may take me a while though, I am getting busy very fast :(
>
> On 2020-01-01 21:30, Pedro Giffuni wrote:
>> Hello AOO devs and best wishes for the New Year!
>>
>> Well ... time has passed and Python 2 is now deprecated!
>>
>> I have a patch here to update AOO 4.2's version of Python to the latest
>> (perhaps last) release in that line:
>>
>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>
>> This is a remake of the previous update that I had made for
>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>> with git so please someone else will have to test and commit.
>>
>> On the near term, we really should update to Python 3, but that will be
>> challenging for the build system since it requires a newer version of
>> the MS compiler.
>>
>> Building with an external python is also currently broken for python
>> versions >= 3.6.
>>
>> Regards,
>>
>> Pedro.
>>
Re: Update to python-2.17
Posted by Pedro Giffuni <pf...@apache.org>.
Hi Matthias;
Sorry about that. I could've tested better the patch. I will fix the
obvious issues and will let you guys know.
Pedro.
ps. It may take me a while though, I am getting busy very fast :(
On 2020-01-01 21:30, Pedro Giffuni wrote:
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
>
> On the near term, we really should update to Python 3, but that will be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
Best wishes for 2020 from me.
Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
Thanks, I have applied your patch to my local repo and will build with
it for Windows now.
If it is successful and nobody else is willing to try it I will commit
it to trunk.
Regards,
Matthias
>
> On the near term, we really should update to Python 3, but that will be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Peter,
Am 23.04.20 um 10:04 schrieb Peter Kovacs:
> Hi all,
>
>
> I have replaced everything 2.7.17 to 2.7.18. Added the Python file in
> downloads.
>
> I would do now a test build.
Great!
>
> After the test build how can I test if there are issues?
Simply run the Python scripts in Writer. That's what I did... ;-)
Regards,
Matthias
>
>
> All the best
>
> Peter
>
> Am 21.04.20 um 18:40 schrieb Matthias Seidel:
>> Hi Marcus,
>>
>> Am 21.04.20 um 18:33 schrieb Marcus:
>>> Am 21.04.20 um 13:56 schrieb Matthias Seidel:
>>>> The final Python 2.7.18 is out:
>>>>
>>>> https://www.python.org/downloads/release/python-2718/
>>>>
>>>> I would expect no major changes to 2.7.17, so we could probably update
>>>> to that version?
>>> is currently version 2.7.17 included? If so, then updating to .18 for
>>> testing could be done.
>>>
>>> Otherwise a more complicated update phase from somewhere to 2.7.18
>>> should be done first.
>> Pedro did the update to 2.1.17 early this year [1].
>>
>> So updating to the final 2.7.18 should be only minor adjustments.
>>
>> Regards,
>>
>> Matthias
>>
>> [1] https://github.com/apache/openoffice/pull/23
>>
>>> My 2 ct.
>>>
>>> Marcus
>>>
>>>
>>>
>>>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>>>> Hello AOO devs and best wishes for the New Year!
>>>>>
>>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>>
>>>>> I have a patch here to update AOO 4.2's version of Python to the
>>>>> latest
>>>>> (perhaps last) release in that line:
>>>>>
>>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>>
>>>>> This is a remake of the previous update that I had made for
>>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>>> with git so please someone else will have to test and commit.
>>>>>
>>>>> On the near term, we really should update to Python 3, but that
>>>>> will be
>>>>> challenging for the build system since it requires a newer version of
>>>>> the MS compiler.
>>>>>
>>>>> Building with an external python is also currently broken for python
>>>>> versions >= 3.6.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Update to python-2.17
Posted by Peter Kovacs <pe...@apache.org>.
Hi all,
I have replaced everything 2.7.17 to 2.7.18. Added the Python file in
downloads.
I would do now a test build.
After the test build how can I test if there are issues?
All the best
Peter
Am 21.04.20 um 18:40 schrieb Matthias Seidel:
> Hi Marcus,
>
> Am 21.04.20 um 18:33 schrieb Marcus:
>> Am 21.04.20 um 13:56 schrieb Matthias Seidel:
>>> The final Python 2.7.18 is out:
>>>
>>> https://www.python.org/downloads/release/python-2718/
>>>
>>> I would expect no major changes to 2.7.17, so we could probably update
>>> to that version?
>> is currently version 2.7.17 included? If so, then updating to .18 for
>> testing could be done.
>>
>> Otherwise a more complicated update phase from somewhere to 2.7.18
>> should be done first.
> Pedro did the update to 2.1.17 early this year [1].
>
> So updating to the final 2.7.18 should be only minor adjustments.
>
> Regards,
>
> Matthias
>
> [1] https://github.com/apache/openoffice/pull/23
>
>> My 2 ct.
>>
>> Marcus
>>
>>
>>
>>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>>> Hello AOO devs and best wishes for the New Year!
>>>>
>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>
>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>> (perhaps last) release in that line:
>>>>
>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>
>>>> This is a remake of the previous update that I had made for
>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>> with git so please someone else will have to test and commit.
>>>>
>>>> On the near term, we really should update to Python 3, but that will be
>>>> challenging for the build system since it requires a newer version of
>>>> the MS compiler.
>>>>
>>>> Building with an external python is also currently broken for python
>>>> versions >= 3.6.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Marcus,
Am 21.04.20 um 18:33 schrieb Marcus:
> Am 21.04.20 um 13:56 schrieb Matthias Seidel:
>> The final Python 2.7.18 is out:
>>
>> https://www.python.org/downloads/release/python-2718/
>>
>> I would expect no major changes to 2.7.17, so we could probably update
>> to that version?
>
> is currently version 2.7.17 included? If so, then updating to .18 for
> testing could be done.
>
> Otherwise a more complicated update phase from somewhere to 2.7.18
> should be done first.
Pedro did the update to 2.1.17 early this year [1].
So updating to the final 2.7.18 should be only minor adjustments.
Regards,
Matthias
[1] https://github.com/apache/openoffice/pull/23
>
> My 2 ct.
>
> Marcus
>
>
>
>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>> Hello AOO devs and best wishes for the New Year!
>>>
>>> Well ... time has passed and Python 2 is now deprecated!
>>>
>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>> (perhaps last) release in that line:
>>>
>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>
>>> This is a remake of the previous update that I had made for
>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>> with git so please someone else will have to test and commit.
>>>
>>> On the near term, we really should update to Python 3, but that will be
>>> challenging for the build system since it requires a newer version of
>>> the MS compiler.
>>>
>>> Building with an external python is also currently broken for python
>>> versions >= 3.6.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Update to python-2.17
Posted by Marcus <ma...@wtnet.de>.
Am 21.04.20 um 13:56 schrieb Matthias Seidel:
> The final Python 2.7.18 is out:
>
> https://www.python.org/downloads/release/python-2718/
>
> I would expect no major changes to 2.7.17, so we could probably update
> to that version?
is currently version 2.7.17 included? If so, then updating to .18 for
testing could be done.
Otherwise a more complicated update phase from somewhere to 2.7.18
should be done first.
My 2 ct.
Marcus
> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>> Hello AOO devs and best wishes for the New Year!
>>
>> Well ... time has passed and Python 2 is now deprecated!
>>
>> I have a patch here to update AOO 4.2's version of Python to the latest
>> (perhaps last) release in that line:
>>
>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>
>> This is a remake of the previous update that I had made for
>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>> with git so please someone else will have to test and commit.
>>
>> On the near term, we really should update to Python 3, but that will be
>> challenging for the build system since it requires a newer version of
>> the MS compiler.
>>
>> Building with an external python is also currently broken for python
>> versions >= 3.6.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Peter Kovacs <pe...@apache.org>.
Hi all,
My test build has been successful and I was able to execute a python code.
This afternoon I hope I can push the changes for the migration to github
for review.
All the best
Peter
Am 23.04.20 um 15:24 schrieb Matthias Seidel:
> Hi Jim,
>
> Am 23.04.20 um 15:21 schrieb Jim Jagielski:
>>> On Apr 23, 2020, at 8:50 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>>
>>> Hi Jim,
>>>
>>> Am 23.04.20 um 13:42 schrieb Jim Jagielski:
>>>> I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version.
>>> In trunk and AOO42X we are already on 2.7.17. No problems so far.
>> Yeah, I think in trunk and AOO42X we should just go w/ 2.7.18... Bite the bullet now.
> I really don't expect problems here. Let's see what Peter can say about
> his test build.
>
> Matthias
>
>>> But in 4.1.7 we still ship 2.7.6 (?).
>> I agree that we don't mess w/ 4.1.X
>>
>>> Regards,
>>>
>>> Matthias
>>>
>>>>> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> The final Python 2.7.18 is out:
>>>>>
>>>>> https://www.python.org/downloads/release/python-2718/
>>>>>
>>>>> I would expect no major changes to 2.7.17, so we could probably update
>>>>> to that version?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Matthias
>>>>>
>>>>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>>>>> Hello AOO devs and best wishes for the New Year!
>>>>>>
>>>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>>>
>>>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>>>> (perhaps last) release in that line:
>>>>>>
>>>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>>>
>>>>>> This is a remake of the previous update that I had made for
>>>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>>>> with git so please someone else will have to test and commit.
>>>>>>
>>>>>> On the near term, we really should update to Python 3, but that will be
>>>>>> challenging for the build system since it requires a newer version of
>>>>>> the MS compiler.
>>>>>>
>>>>>> Building with an external python is also currently broken for python
>>>>>> versions >= 3.6.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Pedro.
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>
>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Jim,
Am 23.04.20 um 15:21 schrieb Jim Jagielski:
>
>> On Apr 23, 2020, at 8:50 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>
>> Hi Jim,
>>
>> Am 23.04.20 um 13:42 schrieb Jim Jagielski:
>>> I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version.
>> In trunk and AOO42X we are already on 2.7.17. No problems so far.
> Yeah, I think in trunk and AOO42X we should just go w/ 2.7.18... Bite the bullet now.
I really don't expect problems here. Let's see what Peter can say about
his test build.
Matthias
>
>> But in 4.1.7 we still ship 2.7.6 (?).
> I agree that we don't mess w/ 4.1.X
>
>> Regards,
>>
>> Matthias
>>
>>>> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> The final Python 2.7.18 is out:
>>>>
>>>> https://www.python.org/downloads/release/python-2718/
>>>>
>>>> I would expect no major changes to 2.7.17, so we could probably update
>>>> to that version?
>>>>
>>>> Regards,
>>>>
>>>> Matthias
>>>>
>>>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>>>> Hello AOO devs and best wishes for the New Year!
>>>>>
>>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>>
>>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>>> (perhaps last) release in that line:
>>>>>
>>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>>
>>>>> This is a remake of the previous update that I had made for
>>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>>> with git so please someone else will have to test and commit.
>>>>>
>>>>> On the near term, we really should update to Python 3, but that will be
>>>>> challenging for the build system since it requires a newer version of
>>>>> the MS compiler.
>>>>>
>>>>> Building with an external python is also currently broken for python
>>>>> versions >= 3.6.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Pedro.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Update to python-2.17
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Apr 23, 2020, at 8:50 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>
> Hi Jim,
>
> Am 23.04.20 um 13:42 schrieb Jim Jagielski:
>> I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version.
> In trunk and AOO42X we are already on 2.7.17. No problems so far.
Yeah, I think in trunk and AOO42X we should just go w/ 2.7.18... Bite the bullet now.
>
> But in 4.1.7 we still ship 2.7.6 (?).
I agree that we don't mess w/ 4.1.X
>
> Regards,
>
> Matthias
>
>>
>>> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>>
>>> Hi all,
>>>
>>> The final Python 2.7.18 is out:
>>>
>>> https://www.python.org/downloads/release/python-2718/
>>>
>>> I would expect no major changes to 2.7.17, so we could probably update
>>> to that version?
>>>
>>> Regards,
>>>
>>> Matthias
>>>
>>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>>> Hello AOO devs and best wishes for the New Year!
>>>>
>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>
>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>> (perhaps last) release in that line:
>>>>
>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>
>>>> This is a remake of the previous update that I had made for
>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>> with git so please someone else will have to test and commit.
>>>>
>>>> On the near term, we really should update to Python 3, but that will be
>>>> challenging for the build system since it requires a newer version of
>>>> the MS compiler.
>>>>
>>>> Building with an external python is also currently broken for python
>>>> versions >= 3.6.
>>>>
>>>> Regards,
>>>>
>>>> Pedro.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Jim,
Am 23.04.20 um 13:42 schrieb Jim Jagielski:
> I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version.
In trunk and AOO42X we are already on 2.7.17. No problems so far.
But in 4.1.7 we still ship 2.7.6 (?).
Regards,
Matthias
>
>> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>>
>> Hi all,
>>
>> The final Python 2.7.18 is out:
>>
>> https://www.python.org/downloads/release/python-2718/
>>
>> I would expect no major changes to 2.7.17, so we could probably update
>> to that version?
>>
>> Regards,
>>
>> Matthias
>>
>> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>>> Hello AOO devs and best wishes for the New Year!
>>>
>>> Well ... time has passed and Python 2 is now deprecated!
>>>
>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>> (perhaps last) release in that line:
>>>
>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>
>>> This is a remake of the previous update that I had made for
>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>> with git so please someone else will have to test and commit.
>>>
>>> On the near term, we really should update to Python 3, but that will be
>>> challenging for the build system since it requires a newer version of
>>> the MS compiler.
>>>
>>> Building with an external python is also currently broken for python
>>> versions >= 3.6.
>>>
>>> Regards,
>>>
>>> Pedro.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Update to python-2.17
Posted by Jim Jagielski <ji...@jaguNET.com>.
I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version.
> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <ma...@hamburg.de> wrote:
>
> Hi all,
>
> The final Python 2.7.18 is out:
>
> https://www.python.org/downloads/release/python-2718/
>
> I would expect no major changes to 2.7.17, so we could probably update
> to that version?
>
> Regards,
>
> Matthias
>
> Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
>> Hello AOO devs and best wishes for the New Year!
>>
>> Well ... time has passed and Python 2 is now deprecated!
>>
>> I have a patch here to update AOO 4.2's version of Python to the latest
>> (perhaps last) release in that line:
>>
>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>
>> This is a remake of the previous update that I had made for
>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>> with git so please someone else will have to test and commit.
>>
>> On the near term, we really should update to Python 3, but that will be
>> challenging for the build system since it requires a newer version of
>> the MS compiler.
>>
>> Building with an external python is also currently broken for python
>> versions >= 3.6.
>>
>> Regards,
>>
>> Pedro.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi all,
The final Python 2.7.18 is out:
https://www.python.org/downloads/release/python-2718/
I would expect no major changes to 2.7.17, so we could probably update
to that version?
Regards,
Matthias
Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
>
> On the near term, we really should update to Python 3, but that will be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: Update to python-2.17
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Pedro,
After fixing a little problem with PYMICRO, I could start to build.
But at some point the process simply stops. I don't know why, will try
again this weekend. Maybe some others have better luck?
Regards,
Matthias
Am 02.01.20 um 03:30 schrieb Pedro Giffuni:
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
>
> On the near term, we really should update to Python 3, but that will be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: Update to python-2.17
Posted by Bidouille <oo...@free.fr>.
Hello Pedro and all the best for you too,
Remember we have an issue for that:
https://bz.apache.org/ooo/show_bug.cgi?id=123975
----- Mail original -----
> De: "Pedro Giffuni" <pf...@apache.org>
> À: dev@openoffice.apache.org
> Envoyé: Jeudi 2 Janvier 2020 03:30:03
> Objet: Update to python-2.17
>
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the
> latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
>
> On the near term, we really should update to Python 3, but that will
> be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org