I at the moment have Python3 as model 3.12.4 in my PATH. It was put in through Homebrew.
I’ve put in mkdocs utilizing
pip3 set up mkdocs
mkdocs --version says
mkdocs, model 1.6.0 from /Customers/ronaldfischer/Library/Python/3.11/lib/python/site-packages/mkdocs (Python 3.11)
It mentions Python 3.11 as a result of at time of set up, my Python3 within the PATH was nonetheless 3.11. In the meantime, one other homebrew set up up to date Python to three.12, so that is what I am working now.
Once I do a mkdocs serve, I get the error message
can’t discover module ‘pymdownx.superfences’ (No module named ‘pymdownx’)
(superfences is referenced to within the mkdocs.yml file)
I figured that I want to put in pymdown-extensions. My first method
pip3 set up pymdown-extensions
failed with error message
*This setting is externally managed. … If you happen to want to set up a Python utility that is not in Homebrew, it might be best to make use of ‘pipx set up xyz’.
So I put in pipx through Homebrew after which executed
pipx --include-deps pymdown-extensions
and added ~/.native/bin to my PATH. My .native/bin comprises now a symlink
markdown_py -> /Customers/ronaldfischer/.native/pipx/venvs/pymdown-extensions/bin/markdown_py
Nevertheless, I nonetheless get the error message when working mkdocs.
Once I do a
discover ~ -name '*pymdownx*' 2>/dev/null
I do not get any matching recordsdata. This makes me ponder whether the bundle is appropriately put in.
What did I do fallacious, and – extra importantly – how can I repair it?
UPDATE
I’ve not set the setting variable PYTHONPATH, because the docs about mkdocs do not point out it. I simply marvel how my put in packages are alleged to be discovered with out this variable.