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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,18 +125,18 @@ While you're in a venv, the `python` command will point to whatever version you
125
125
126
126
## Installing dependencies
127
127
128
-
The packages you need to run CVE Binary Tool are listed in the `requirements.txt` file in the main cve-bin-tool directory. You can install all of them using the following pip command:
128
+
The packages you need to run CVE Binary Tool are listed in the `dependencies` section of the `pyproject.toml` file in the main cve-bin-tool directory. You can install all of them using the following pip command:
129
129
130
130
```bash
131
-
pip install -U -r requirements.txt
131
+
pip install -U -r .
132
132
```
133
133
134
-
The `-U` in that line above will update you to the latest versions of packages as needed, which we recommend because people running security tools generally want to have all the latest updates if possible. The `-r requirements.txt` specifies the file with all the requirements.
134
+
The `-U` in that line above will update you to the latest versions of packages as needed, which we recommend because people running security tools generally want to have all the latest updates if possible.
135
135
136
136
We also have a recommended list of dependencies just for developers that include things like the flake8 linter. You probably want to install them too if you're intending to be a developer.
137
137
138
138
```bash
139
-
pip install -r dev-requirements.txt
139
+
pip install -r .[dev]
140
140
```
141
141
142
142
## Running your local copy of CVE Binary Tool
@@ -183,7 +183,7 @@ pip install -e .
183
183
184
184
The CVE Binary Tool has a set of tests that can be run using `pytest` command. Typically you want to run `pytest` in the cve-bin-tool directory to run the short test suite and make sure tests pass.
185
185
186
-
After running `pytest`, you may get several test failures relating to `ModuleNotFound` error. If you have run `pip install -r dev-requirements.txt` or equivalent and are sure you have the required modules installed, your issue may be related to Python's module search path. You can run this command instead :
186
+
After running `pytest`, you may get several test failures relating to `ModuleNotFound` error. If you have run `pip install -r .[dev]` or equivalent and are sure you have the required modules installed, your issue may be related to Python's module search path. You can run this command instead :
187
187
188
188
```bash
189
189
python -m pytest
@@ -211,10 +211,10 @@ CVE Binary Tool uses a few tools to improve code quality and readability:
211
211
-`interrogate` checks your code base for missing docstrings.
212
212
-`codespell` Detects common misspellings in text files.
213
213
214
-
We provide a `dev-requirements.txt` file which includes all the precise versions of tools as they'll be used in GitHub Actions. You an install them all using pip:
214
+
We have a list of optional dev dependencies in our `pyproject.toml` file which includes all the precise versions of tools as they'll be used in GitHub Actions. You can install them all using pip:
0 commit comments