You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's common to make a virtualenv inside of your cloned repo
to ensure that you have the right enviornment for that repository,
and .venv is a common convention for that virtualenv.
This adds targets to create and clean a .venv virtual env using
the checked-in requirements.txt file. It also adds the .venv
to the .gitignore, and updates the README.
Copy file name to clipboardExpand all lines: README.md
+9-1
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,15 @@ Labels are assigned based on [Sensible Github Labels](https://github.com/Releque
35
35
* links.json - JSON Hyper-Schema's Link Description Object meta-schema
36
36
* hyper-schema-output.json - The recommended output format for JSON Hyper-Schema links
37
37
38
-
Install "xml2rfc" using "pip" (https://pypi.org/project/xml2rfc/) and type "make" at a shell to build the .txt and .html spec files:
38
+
The Makefile can create the necessary Python virtual environment for you:
39
+
40
+
```sh
41
+
make venv
42
+
source .venv/bin/activate
43
+
make
44
+
```
45
+
46
+
Or you can manually install "xml2rfc" using "pip" (https://pypi.org/project/xml2rfc/) and type "make" at a shell to build the .txt and .html spec files:
0 commit comments