[core] plugins: Correctly handle installed virtual envs on Linux #2886
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the initialization logic for the
DirTreeProcessEnvclass inmeshroom/core/plugins.pyto improve support for plugins that use virtual environments. The changes make the environment setup more robust by explicitly handling the presence of avenvdirectory and ensuring paths are correctly added for both standard and virtual environment layouts.Prior to this PR, virtual environments were correctly handled on Windows (with specific venv layout for Windows) but were not taken into account for Linux, for which we were only relying on the standard "bin"/"lib"/"lib64" structure. Both layouts are now supported at the same time, meaning a plugin can theoretically have the following structure:
In practice, virtual environments are generally not used at the same time as the standard "bin"/"lib"/"lib64" layout.