CPythonInvoker: fix python path by inserting custom path before default path #23244
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.
This fixes #22985 reported by @matthuisman
#21704 changed the way the python path order was handled. It put the custom python path after the default python path. This causes an issue where custom python modules are used for a specific add-on and the same module was installed on the system python path. The system python path would be ordered before the custom python path.
This PR inserts the custom python path at the beginning of the python path instead of the end.
I also made a minor change to the way the paths are logged. I'm not sure if that is desired or not.
Before:
After:
The diff looks messy and is better viewed in the split view -> link
What is the effect on users?
allows add-ons to work properly by allowing custom python modules to be preferred.