integrating meta-python layer and library dependencies about meta-iot2000 HOT 14 CLOSED

MRAA is not part of meta-iot2000. We rather pull its recipes from meta-openembedded now (meta-intel-iot-middleware, the former source, is dead by now).

from meta-iot2000.

A few other libs/tools that would be useful to have, if possible, are:

• PyPy for Python2.7
• easy_install -- part of the python setuptools (Python2.7 also)

from meta-iot2000.

OK, can be added.

But I would refrain from adding those dependencies in legacy python-2.7 form anymore. Yocto moved on to python 3, and those 2.7 packages may break or get removed. Any concerns about that constraint?

from meta-iot2000.

BTW, python3-pip and python3-modules are already part of our image. Adding python3-setuptools and python3-lxml now, then checking what the latter already pulls in automatically.

Unfortunately, PyPy looks much more complex on second sight. I would recommend building it manually using our cross-toolchain.

from meta-iot2000.

Well, in that case, Python 3 should be fine.
As for PyPy, sure, I'll look into building it using the cross-toolchain. Thanks.

from meta-iot2000.

I've pushed jan/python-addons with the aforementioned additional packages. Let me know if that is already sufficient, then we can start a PR.

from meta-iot2000.

I managed to install the libs that I was looking for without needing the easy_install tool, so on my side, I wouldn't need any new additional package on the image.

from meta-iot2000.

@laura-mc can we close the issue by sending out this change for master, or is still something missing?

from meta-iot2000.

@jan-kiszka I think it is complete, I would send it.

from meta-iot2000.

merged into master

from meta-iot2000.

I would like to reopen this issue as I'm unable to install pip2.
Python2.7 is/was strongly needed as the MRAA Library is/was only available in Python2.7
(since when is MRAA available for Python3?? My build from 06.May.2018 does not contain it? But my new Image from 15. August.2018 contains MRAA for Python3)

I solved this issue back then by loading a few necessary libraries first from the opkg sources and two missing ones directly from github.com/python/cpython/lib

With the new image I hoped to transfer the missing libraries from the old to the new image.
But this is not working flawless as I need zlib and some other core libs like xml to be installed properly.

Hm. Now I am a bit uncertain what to do. I think the best would be to transfer my code to Python3.

Nevertheless can someone say me if MRAA was recently added as a Python3 library in the example image or was this just a missing configuration from my site?

Cheers

from meta-iot2000.

In master (and thus for the upcoming release), we moved to Python 3 as default. MRAA is also Python 3 now, primarily because the upstream recipes changed this way, but also because it's general standard. So you should move your application to Python 3 which is typically not a big deal.

PS: This issue is still closed. Please open a new one if you find problems with the master version.

from meta-iot2000.

Thank you for the fast reply. Python3 should be no issue for me. It was just a pita to make my whole system work with Python2.7 just to find out that MRAA also works with Python3 now.

So MRAA happend to merge into master inbetween my two builds is this right?
Sorry for the confusion in my comment before. I was just uncertain what to do now finding the Python3 integration halfway writing this comment as I was checking the facts.. 😆

Just want to confirm this integration and I'm happy with it.. 🍶

from meta-iot2000.

Thank you for this information :) Now I have some more facts for my bachelor thesis.

from meta-iot2000.