lightning/requirements
Adrian Wälchli be9761e5c4
Simplify step redirection in strategy (#17531)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Jirka Borovec <6035284+Borda@users.noreply.github.com>
2023-06-05 11:38:56 +00:00
..
_integrations Simplify step redirection in strategy (#17531) 2023-06-05 11:38:56 +00:00
app Update deepdiff requirement from <6.2.4,>=5.7.0 to >=5.7.0,<6.3.1 in /requirements (#17631) 2023-05-29 14:44:25 +00:00
fabric Upgrade deepspeed version (#17748) 2023-06-05 10:28:30 +00:00
pytorch Upgrade deepspeed version (#17748) 2023-06-05 10:28:30 +00:00
README.md Remove devel.txt requirements file (#17466) 2023-04-25 07:21:21 +00:00
collect_env_details.py Remove duplicate import checks (#16648) 2023-05-04 18:40:42 +02:00
docs.txt Update numpy requirement from <1.24.2,>=1.17.2 to >=1.17.2,<1.24.4 in /requirements (#17538) 2023-05-02 13:48:26 +00:00
typing.txt Bump mypy from 1.1.1 to 1.2.0 in /requirements (#17535) 2023-05-01 15:35:24 +02:00

README.md

Project Requirements

This root requirements folder branches into sub-folders depending on the python package. Within the folder, we have grouped requirements files/lists per focus, which shall closely match package extra So, for example, when you install PL as pip install pytorch-lightning[extra], this list is stored in requirements/pytorch/extra.txt.

CI/CD upper bounds

For Ci stability, we have set for all package versions upper bounds (the latest version), so with any sudden release, we won't put our development on fire. The continues updated of these upper bounds are managed by dependabot. Note that these upper bounds are lifters when installing a package from the source or as a package. If you want to preserve/enforce restrictions on the latest compatible version, add "strict" as an in-line comment.