Skip to content

Install lmr python tooling to virtual environment - #151

Open
Alex-Muirhead wants to merge 4 commits into
masterfrom
lmr-python-installs
Open

Install lmr python tooling to virtual environment#151
Alex-Muirhead wants to merge 4 commits into
masterfrom
lmr-python-installs

Conversation

@Alex-Muirhead

Copy link
Copy Markdown
Collaborator

A subset of #149, testing on lmr in isolation.
Please test out, and report any issues.

Alex-Muirhead and others added 3 commits August 6, 2026 10:37
Previously the lmr python tooling was installed as editable.
This provided the benefit of immediate updates to the tooling when source code was changed, without re-installing.
However, it required the source repository to stay present, which is not guaranteed on limited systems.
- Update PyEnv install script for lmr-tooling to use a relative path (by prefixing with `./`), to avoid pip searching for a package with the directory name.
@Alex-Muirhead

Copy link
Copy Markdown
Collaborator Author

At this point, the workflow for installing the Python program for lmr (which is only lmr-verify at the moment) is simply make install from within the lmr directory.

The existence (or absence) of PYTHONPATH has no impact on Python executable programs, however the warning is added for future packaging of the gdtk Python library.

For the sake of consistency with previous installs, if PYTHONPATH is set and contains the $INSTALL_DIR/lib location, we assume the user is following the original instructions, and has system-wide installs of Python tooling. The installation then falls back to the original method (a simple cp to the $INSTALL_DIR/bin directory), and lets the user handle the externally managed system.
The user can also opt-in to this method by setting USE_PYTHONPATH=1 when calling make install.

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.

1 participant