echo your $PATH & site-packages after activating venv. The activation logic does some juggling with the PATH so maybe pandoc slipped out?
Did you activate your virtual python env with ‘source .venv/bin/activate’? You must do that in each new shell unless you add some config to your shell profile config to have it detect the presence of a python venv.
Yep.
Prompt changes to (venv) foo@bar.
I can run other libraries
Okay perfect, just wanted to check.
Next I’d say check your venv to verify the pandoc binary is indeed there:
find $VIRTUAL_ENV -name pandoc
If it’s not there, you should be able to install it by entering a python shell from your venv and do:
import pypandoc
pypandoc.download_pandoc()
Hopefully that’s able to resolve it for ya. Venv should be at the front of your path so it should prefer bins from there.
Welcome to the Python community on the programming.dev Lemmy instance!
Past
November 2023
October 2023
July 2023
August 2023
September 2023