Fix command for installation of docs dependencies in the guide. #323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is this PR
Why is this PR needed?
movement
in a development environment, and then install a few more additional dependencies to be able to build the docs locally in a later section. In this PR I put both steps in the same section.make clean html
cleans and re-builds the docs, so there is no need to run the build command again as the text suggests.What does this PR do?
The docs
requirements.txt
file specifies the installation of themovement
package on its first line, as-e .
. The dot syntax refers to the current directory (the one executing the command), and it should match the location of themovement
metadata file (pyproject.toml
for us).Since
pyproject.toml
is at the root of the directory, this means the command is expected to be run from the root of the directory too.However, the documentation asks to run the
pip install -r requirements.txt
command from thedocs
directory. If this instructions are followed, we get an error becausepip
is unable to find thepyproject.toml
file for themovement
package.Note that in CI we run the same command that this PR proposes (see here)
References
\
How has this PR been tested?
\
Is this a breaking change?
No.
Does this PR require an update to the documentation?
\
Checklist: