Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Python 3.x script interpreter #543

Closed
sgallou opened this issue Feb 26, 2019 · 13 comments
Closed

Add a Python 3.x script interpreter #543

sgallou opened this issue Feb 26, 2019 · 13 comments
Assignees
Milestone

Comments

@sgallou
Copy link
Contributor

sgallou commented Feb 26, 2019

Python 2.7 seems to become obsolete, add a Python 3.x script interpreter

@sgallou sgallou added this to the 2.3 milestone Feb 26, 2019
@sgallou sgallou self-assigned this Feb 26, 2019
@sgallou sgallou modified the milestones: 2.3, 2.4 May 12, 2019
@sgallou
Copy link
Contributor Author

sgallou commented Jul 5, 2019

Developed but not tested.
Need to update build systems :

  • Update CMake to last version
  • In CMakeListsUserConfig.txt, add :
    • set(PYTHON27_ROOT "xxxx")
    • set(PYTHON3_ROOT "xxxx")
    • keep : set(PYTHON_ROOT "xxxx")
  • Optional : update other dependencies (boost, poco, protobuf, etc...)

@sgallou sgallou assigned jano42 and unassigned sgallou Jul 5, 2019
@jano42
Copy link
Member

jano42 commented Jul 8, 2019

How to update CMakeListsUserConfig.txt when using dpkg mode ?

set(PYTHON_USE_PKGCONFIG ON)
set(PYTHON_USE_SOURCES OFF)

@sgallou
Copy link
Contributor Author

sgallou commented Jul 8, 2019

I think you can't use dpkg mode with the both python interpreters...

@jano42
Copy link
Member

jano42 commented Aug 29, 2019

Fixed in develop branch

@jano42 jano42 closed this as completed Aug 29, 2019
@sgallou sgallou reopened this Dec 19, 2019
@sgallou
Copy link
Contributor Author

sgallou commented Dec 19, 2019

Interpreters (2.7 & 3) doesn't work on Linux and Mac. Must understand why (=> SG).

But should we :

  • Embed Python with Yadoms ? Be careful to cross-build (=> to be tested by JMD), and don't forget to provide pip)
  • Add .ini file to let user to specify python executable path ?

@sgallou sgallou self-assigned this Dec 19, 2019
@jano42
Copy link
Member

jano42 commented Dec 19, 2019

Both !

One to be sure all is working as expected in nominal case.
The second, if too hard to embed python (some obscur platform) or user want to test another version of python

@sgallou
Copy link
Contributor Author

sgallou commented May 13, 2020

Add .ini (specific to interpreter) to provide Python executable folder, and use it by default.

@sgallou
Copy link
Contributor Author

sgallou commented May 29, 2020

Specific ini file to interpreter is problematic : this kind of file can not be backuped (no saved 'data' folder like for plugins), and isolated in yadoms executable hierarchy.
I suggest to add the forced paths in the general yadoms.ini file.

@jano42
Copy link
Member

jano42 commented May 29, 2020

Yes it easier
In yadoms.ini file you could provide a section of config for interpreters

For example:


[interpreter/python2]
pyhtonPath=.....

[interpreter/python3]
pyhtonPath=.....

@sgallou
Copy link
Contributor Author

sgallou commented May 29, 2020

Fixed by 9454b69
Need to be tested on all platforms

@oben01
Copy link
Member

oben01 commented May 29, 2020

python 2.7 and python 3 are installed by default in mac OS Catallina.
test python 2.7 ==> OK
test python 3.7.3 ==> OK
blokly => OK

tests are made from develop branch

@oben01
Copy link
Member

oben01 commented May 29, 2020

@sgallou do you need me to install another python 3 version by hand and test it ?

@sgallou
Copy link
Contributor Author

sgallou commented Jun 3, 2020

@sgallou do you need me to install another python 3 version by hand and test it ?

No, 3.7.3 is OK. Thanks for your test.

@sgallou sgallou closed this as completed in 9454b69 Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants