python(3) .so files and Harbour...
asked 2019-03-18 16:17:56 +0200
Because the python vulnerability fix was just upgrading python3 from 3.4 to 3.7 (!): Are there any clues how to manage self compiled libraries for python and harbour?
Are they allowed? How to double deliver for 3.4 and 3.7 with /usr/share/harbour/myapp/lib/python3.x/site-packages?
(I just build a libolm-support and with 3.0.2 it needs a recompile because of 3.7)
How can one / did you upgrade to python 3.7? I would also be interested in a newer python version, because of asyncio (with async/await syntax).
Mario ( 2019-03-18 17:34:12 +0200 )editSFOS 3.0.2.8 introduces Python 3.7.2
Nieldk ( 2019-03-18 18:57:16 +0200 )editIt is not the upgrade to 3.7.x (that is great). It is the upgrade "politics" here: I just got python-olm running (for this https://gitlab.com/cy8aer/bluepill). It has binary libs compiled against 3.4. Now I need to wait for the next sdk. Allowing Python in harbour is nice but it does not work at the point where you need more than simple python modues.
And: it is complicated to provide both versions so that everyone can use it.
cy8aer ( 2019-03-18 20:19:08 +0200 )edit@cy8aer Maybe the Mer OBS targets have already been updated ? https://build.merproject.org/
MartinK ( 2019-03-19 03:44:22 +0200 )editThis is great news! Thanks for the info. And sorry for hijacking your thread, but I'm still on 3.0.1.11 and was quite puzzled about hearing of python 3.7 (which I really wished for in the next Sailfish update, but didn't actually dream of).
Mario ( 2019-03-19 22:59:26 +0200 )edit