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

PYTHON not set correctly in export.sh #2759

Merged
merged 1 commit into from
Apr 10, 2024

Conversation

mikee47
Copy link
Contributor

@mikee47 mikee47 commented Apr 10, 2024

The PYTHON environment variable isn't set correctly for CI builds, or for other installations where non-standard locations may be used. This can result in unexpected behaviour where multiple python3 versions are installed.

Update to #2735.

Copy link

what-the-diff bot commented Apr 10, 2024

PR Summary

  • Modification of 'export.sh' File
    The 'export.sh' file located in the 'Tools' directory has been updated. This change is integral to ensure the correct operation of our software tools.

  • Environment Variable Update for PYTHON
    We've adjusted how the PYTHON environment variable is set. Now, it uses an automatic system command (which python3) to identify the location of Python3 on your computer. This enhancement makes it easier for the system to interface with Python, irrespective of where it's installed on your computer.

@slaff slaff added this to the 5.2.0 milestone Apr 10, 2024
@slaff slaff merged commit 39f0cf6 into SmingHub:develop Apr 10, 2024
46 checks passed
@mikee47 mikee47 deleted the fix/PYTHON-not-set branch April 10, 2024 11:42
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