lightning/requirements
Adrian Wälchli dfb687aa28
Bump minimum wandb version from 0.12.0 to 0.12.10 (#18171)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
2023-07-27 05:31:24 -04:00
..
_integrations Simplify step redirection in strategy (#17531) 2023-06-05 11:38:56 +00:00
app Bump pytest from 7.3.1 to 7.4.0 in /requirements (#18038) 2023-07-26 22:40:36 +00:00
data Bump pytest from 7.3.1 to 7.4.0 in /requirements (#18038) 2023-07-26 22:40:36 +00:00
fabric Bump pytest from 7.3.1 to 7.4.0 in /requirements (#18038) 2023-07-26 22:40:36 +00:00
pytorch Bump minimum wandb version from 0.12.0 to 0.12.10 (#18171) 2023-07-27 05:31:24 -04: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 myst-parser requirement from <1.0.0,>=0.18.1 to >=0.18.1,<3.0.0 in /requirements (#18142) 2023-07-26 10:12:29 +02:00
typing.txt bump Lit-Utils to 0.9 (#17955) 2023-07-03 17:49:00 +00: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.