error: externally-managed-environment about greaseweazle HOT 8 CLOSED

Another alternative is to use pipx which manages all the venv stuff automatically and probably puts gw on your default path. I will investigate that and possibly recommend that instead.

from greaseweazle.

Okay, pipx looks pretty neat. I updated the instructions to recommend this new method. I think it is more along the lines of what you'd expect as an experience.

from greaseweazle.

Yes, many distros are moving to require using a virtual environment for external packages. You can basically use the instructions in the error message, or the virtual environment instructions in the wiki (Linux specific at the moment, but I will extend them for macos).

from greaseweazle.

Okay I've streamlined and updated the wiki instructions. Please let me know how you get on with those.

from greaseweazle.

Closing but please reopen if you see any further issues regarding the updated instructions for using a virtual environment.

from greaseweazle.

OK, it is working now. Thanks for the fast and kind help as always!

But it sure is a bummer that I have to remember this activate command before using the GW software.

from greaseweazle.

You don't have to use the activate command I believe -- you could put the path/to/bin in your PATH variable, or directly specify the path when invoking gw for example greaseweazle/bin/gw

from greaseweazle.

Another alternative is a symlink from a location that is on your default path. I believe default paths are quite locked down in macOS however. I have added some more text to the wiki but, on balance, the easiest thing to do is just remember to activate.

from greaseweazle.