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: README.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ source venv/bin/activate
202
202
# update pip itself if necessary
203
203
python -m pip install -U pip
204
204
# install dependencies (for Python 3.8+)
205
-
python -m pip install -r requirements-310.txt
205
+
python -m pip install -r requirements.in
206
206
```
207
207
208
208
The tests rely on test data in git submodules.
@@ -222,12 +222,27 @@ python -m pytest
222
222
223
223
### Running & Installing pre-commit hooks
224
224
225
-
arrow-datafusion-python takes advantage of [pre-commit](https://pre-commit.com/) to assist developers with code linting to help reduce the number of commits that ultimately fail in CI due to linter errors. Using the pre-commit hooks is optional for the developer but certainly helpful for keeping PRs clean and concise.
225
+
arrow-datafusion-python takes advantage of [pre-commit](https://pre-commit.com/) to assist developers with code linting to help reduce
226
+
the number of commits that ultimately fail in CI due to linter errors. Using the pre-commit hooks is optional for the
227
+
developer but certainly helpful for keeping PRs clean and concise.
226
228
227
-
Our pre-commit hooks can be installed by running `pre-commit install`, which will install the configurations in your ARROW_DATAFUSION_PYTHON_ROOT/.github directory and run each time you perform a commit, failing to complete the commit if an offending lint is found allowing you to make changes locally before pushing.
229
+
Our pre-commit hooks can be installed by running `pre-commit install`, which will install the configurations in
230
+
your ARROW_DATAFUSION_PYTHON_ROOT/.github directory and run each time you perform a commit, failing to complete
231
+
the commit if an offending lint is found allowing you to make changes locally before pushing.
228
232
229
233
The pre-commit hooks can also be run adhoc without installing them by simply running `pre-commit run --all-files`
230
234
235
+
## Running linters without using pre-commit
236
+
237
+
There are scripts in `ci/scripts` for running Rust and Python linters.
238
+
239
+
```shell
240
+
./ci/scripts/python_lint.sh
241
+
./ci/scripts/rust_clippy.sh
242
+
./ci/scripts/rust_fmt.sh
243
+
./ci/scripts/rust_toml_fmt.sh
244
+
```
245
+
231
246
## How to update dependencies
232
247
233
248
To change test dependencies, change the `requirements.in` and run
0 commit comments