Skip to content

Conversation

multiplemonomials
Copy link
Collaborator

Summary of changes

Quick fix here. I noticed that on Windows, even if you configure the python install manager to target a specific Python version, Mbed will still use the most recent version installed (which is often undesirable behavior). I believe that the same thing would happen on Linux, and it would not obey the update-alternatives setting.

Setting these CMake config options seems to cause FindPython to prefer whichever version of Python is pointed to by the python3 or python aliases (as long as it is in the needed version range), which is generally what you want.

Impact of changes

Migration actions required

Documentation

None

Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[X] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

@multiplemonomials multiplemonomials merged commit b9180e7 into master Oct 16, 2025
53 checks passed
@multiplemonomials multiplemonomials deleted the dev/fix-windows-python-launcher branch October 16, 2025 04:50
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