Invoke Path Issues #8827
Labels
bug
Identifies a bug which needs to be addressed
dependency
Relates to a project dependency
docker
Docker / docker-compose
setup
Relates to the InvenTree setup / installation process
Milestone
Overview
A "bug" has been introduced since the merging of #8747 - the
invoke
commands no longer work as expected.Description
When calling
invoke
(used for most system commands), the loaded virtual environment is not used as expected.This occurs when
invoke
is installed as a system-level package which is available onPATH
with higher priority than the version installed in the python virtual environment.The outcome is that calling
invoke <command>
does not use the packages installed in the InvenTree virtual environment.Example - System Invoke
invoke version
- invoke installed at/usr/bin/invoke
Example - venv invoke
python -m invoke version
- called from InvenTree venvOriginally posted by @SchrodingersGat in #8747 (comment)
The text was updated successfully, but these errors were encountered: