The Python build tool, be it poetry or flit or setuptools, will do a build in the environment that the recipe has defined: only the dependencies in DEPENDS, no virtualenv. The point being that we cont

#devtool #python

Hello, I would greatly appreciate any help fixing this issue. I need to install the Python package orjson from PyPI on our Kirkstone build. Since it requires maturin to install I created a recipe for

#python

Good Afternoon, I am updating a project from Honister to Kirkstone, Has anyone else run into an issue with python files with a #!/usr/bin/python header throwing the (abbreviated) Error below? This did

#python #kirkstone

Hi Joshua, It's 100% my fault, I'm mixed 2 variables: ROOTFS_POSTPROCESS_COMMAND IMAGE_POSTPROCESS_COMMAND My "ln " command have to be placed into IMAGE_POSTPROCESS_COMMAND, not ROOTFS_POSTPROCESS_COM

#kirkstone #python #bitbake

I'm working with multiple platforms on dunfell. I'm having trouble understanding the installation step of a couple of pthon3 packages - namely python3-zc-lockfile and python3-jaraco-functools. In both

#python #dunfell

Apologies but I have to say no. Updating these three variables from a bbappend is not a good idea and I strongly recommend that you do not do it. If you need a different version of something, write a

#yocto #python #devtool

if you are using latest release then py2 is more or less not needed unless you use perhaps packages like chromium ( which is also now fixed in meta-browser ) but this is for oe-core and meta-oe layers

#python

Ah OK, I wasn't aware of the the python naming convention. That is likely my problem since I'm using Honister which uses Python 3.9. I pulled the wheel from NVIDIA's forums for pytorch, unfortunately

#bitbake #python

I have a python package hosted in an internal git repo that is currently configured to use Poetry and as such does not have a setup.py file. Yocto appears to expect a setup.py file (via inherit distut

#python

Hey there. I am building a Boot2Qt image for my Jetson Nano. Yocto release is dunfell. Currently I am trying to build the scipy library release 1.5.3. This is the recipe I am using: inherit pypi setup

#python #bitbake

I recommend putting your whole python project into a repository (e.g. with git) and then create a recipe that fetches the git repository and installs the files to a sensible location. You should be ab

#python

Hi All, I'm trying to bitbake a recipe for python3-dlib (the python API). Here is the recipe: SUMMARY = "A toolkit for making real world machine learning and data analysis applications" HOMEPAGE = "ht

#yocto #zeus #python

Thanks for the suggestion, but they are using the C++ API as well. I already created a recipe for the C++ API of dlib and it is working, the only thing needed is compitling the Python API.

#yocto #zeus #python

According to [1] yes - you might want to consider back porting one of the more recent versions of numpy from [2], as you are using a pretty outdated one [1] https://stackoverflow.com/questions/5466584

#yocto #zeus #python

Hello, we are using a recipe to fetch binary from artifactory and package it in rootfile system. and this artifactory path can be dynamic so i am using linux system variable to pass this information t

#python #yocto

Okay, that makes sense! I'll look for a better solution. KR, Felix

#python

(re-adding list as this certainly does not contain sensitive information - others might add other opinions and hints, as well as my answer should be available for everyone to find it.) Am Mo., 22. Feb

#python

Hi I am aware that what I am asking for is a bit ugly. The reason is that I have a small amount of memory at my disposal. I'm working with a setup with two partitions, a root-fs and an overlayed appli

#python

The issue here is that you are overwriting the DEPENDS after the inherit. Two ways to solve this problem Either use DEPENDS = "python3-astropy-helpers" PYPI_PACKAGE = "astropy" inherit pypi or PYPI_PA

#python

Hi there,

#python