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
I'm using a virtual environment to contribute to pandas that sits in a venv directory in the repository root. When I run ./ci/code_checks.sh, all of the linters and checks start to check every single .py file in the virtual environment's site packages, which is a pain. Same happens with the documenation checks and the generated .rst files in doc/source/reference/api.
It would be nice to ensure that the script only runs on files that are being tracked by git, or at least have an option to exclude a directory when doing the checks.
The text was updated successfully, but these errors were encountered:
I'm using a virtual environment to contribute to pandas that sits in a
venv
directory in the repository root. When I run./ci/code_checks.sh
, all of the linters and checks start to check every single.py
file in the virtual environment's site packages, which is a pain. Same happens with the documenation checks and the generated.rst
files indoc/source/reference/api
.It would be nice to ensure that the script only runs on files that are being tracked by git, or at least have an option to exclude a directory when doing the checks.
The text was updated successfully, but these errors were encountered: