Conversation
| > * Exact versions of dependencies: | ||
| > | ||
| > ```bash | ||
| > .venv/bin/pip install -r requirements/requirements-docs.txt # . | ||
| > ``` | ||
| > | ||
| > * Latest versions of all dependencies: | ||
| > | ||
| > ```bash | ||
| > .venv/bin/pip install -r $(properdocs get-deps) # | ||
| > ``` |
There was a problem hiding this comment.
The only issue I have with this, is that maybe people don't know how to use/setup venv?
Also, if they set up one locally (using venv command), then the structure of the folder may differ based on the OS.
There was a problem hiding this comment.
Well this is true, but these instructions are already alternate instructions if you don't want to use Hatch.
I also don't want to recommend installing all the crazy dependencies without a virtualenv.
If you know a straightforward way to make these instructions general also for Windows users, you can follow up in a new pull request
There was a problem hiding this comment.
The only aproach I know is the one that I found in the Material for MkDocs documentation about making a reporoduction:
- use
venv venvto create a venv in the mkdocs folder - use
. venv/Script/activateto activate the venv - Install stuff
- deactivate with
deactivate
I think this is fine for most users tho.
This is because the page is viewable on both GitHub and on the website Also the Python-Markdown parsing of link references is partly broken, so avoid its quirks.
2 participants
No description provided.