ray/python/requirements_linters.txt

flake8==3.9.1
flake8-comprehensions
flake8-quotes==2.0.0
flake8-bugbear==21.9.2
mypy==0.782
black==21.12b0
isort==5.10.1
[CI] Upgrade flake8 to 3.9.1 (#15527) * formatting * format util * format release * format rllib/agents * format rllib/env * format rllib/execution * format rllib/evaluation * format rllib/examples * format rllib/policy * format rllib utils and tests * format streaming * more formatting * update requirements files * fix rllib type checking * updates * update * fix circular import * Update python/ray/tests/test_runtime_env.py * noqa 2021-05-03 14:23:28 -07:00			`flake8==3.9.1`
: Centralize requirements.txt and unify dependency versions (#9759) python_test: fix cython_examples in doc/ and tests/ * update setup.py to parse the bazel version string better * all: centralize all python deps into stackable requirements files in python/ * format * Move cython test into the proper package * Add cross-reference dependency comments for requirements and setup.py * re-enable version pinning on CI, fix formatting * fix up torchvision version * fix case in shell 2020-07-30 11:22:56 -07:00			`flake8-comprehensions`
			`flake8-quotes==2.0.0`
[Lint] Add flake8-bugbear (#19053) * Add flake8-bugbear * Add flake8-bugbear 2021-10-03 23:24:11 -07:00			`flake8-bugbear==21.9.2`
[CI] Add mypy to ci (#11117) * Add mypy check to format.sh * format_all() runs mypy check only on specified files 2020-10-05 14:20:45 -04:00			`mypy==0.782`
[CI] Add support for Black formatting (#21281) 2022-01-03 12:06:41 -06:00			`black==21.12b0`
Add import sorting to format.sh (#25678) It will be easier to develop if we could use a tool to organize / sort imports and not have to move them around by hand. This PR shows how we could do this with isort (black doesn't quite do this per https://github.com/psf/black/issues/333) After this PR lands everyone will need to update their formatter to include isort if they don't have it already, i.e. pip install -r ./python/requirements_linters.txt All future file changes will go through isort and may introduce a slightly larger PR the first time as it will clean up the imports. The plan is to land this PR and also clean up the rest of the code in parallel by using this PR to format the codebase (so people won't get surprised by the formatter if the file hasn't been touched yet) Co-authored-by: Clarence Ng <clarence@anyscale.com> 2022-06-13 14:08:51 -07:00			`isort==5.10.1`