Skip to content

Conversation

@steelman
Copy link

Description

Enable users to choose which Python executable to use to run the agent by setting LG_AGENT_PYTHON environment variable. This is necessary when a remote labgrid runs in a virtual environment which provide packages, or their versions, not available in the system installation of Python.

Checklist

  • Documentation for the feature
  • Tests for the feature
  • PR has been tested
  • Man pages have been regenerated

@codecov
Copy link

codecov bot commented Nov 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.1%. Comparing base (3fc3705) to head (5772c7e).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #1782   +/-   ##
======================================
  Coverage    45.1%   45.1%           
======================================
  Files         172     172           
  Lines       13608   13609    +1     
======================================
+ Hits         6144    6145    +1     
  Misses       7464    7464           
Flag Coverage Δ
3.10 45.1% <100.0%> (+<0.1%) ⬆️
3.11 45.1% <100.0%> (+<0.1%) ⬆️
3.12 45.1% <100.0%> (+<0.1%) ⬆️
3.13 45.1% <100.0%> (+<0.1%) ⬆️
3.14 45.1% <100.0%> (+<0.1%) ⬆️
3.9 45.1% <100.0%> (+<0.1%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Enable users to choose which Python executable to use to run the
agent by setting LG_AGENT_PYTHON environment variable. This is necessary
when a remote labgrid runs in a virtual environment which provide
packages, or their versions, not available in the system installation
of Python.

Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
@jluebbe
Copy link
Member

jluebbe commented Dec 2, 2025

Doesn't this mean that the same path would be used for all exporters? When you have a diverse set of exporters, a fixed interpreter wouldn't work well.

@steelman
Copy link
Author

steelman commented Dec 2, 2025

I haven't thought about connecting to many different exporters at once, indeed. In such case, I suppose, each exporter should advertise the interpreter it uses and clients need to discover it.

@jluebbe
Copy link
Member

jluebbe commented Dec 3, 2025

For which dependencies do you need a virtualenv? We've tried to avoid complex dependencies, so (in our setups) installing the few needed dependencies using distro packages worked well. Especially for NetworkManager, you want to use the packages which match the libnm from the distro.

@steelman
Copy link
Author

steelman commented Dec 3, 2025

I've got patches to introduce support for FTDI chips in bitbanging mode to control relays (which enables using 8 pins instead of 3-4 when controlled via Linux gpio driver). For this to work pyftdi needs to be patched as well. We figure the patches won't make it into Ubuntu anytime soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants