lightning/requirements
Justus Schock 7ca49f2cb7
Requirements update (#18014)
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
2023-07-10 13:00:20 +00:00
..
_integrations Simplify step redirection in strategy (#17531) 2023-06-05 11:38:56 +00:00
app pin `pydantic <2.0` (#18022) 2023-07-08 16:04:38 +02:00
data bump Lit-Utils to 0.9 (#17955) 2023-07-03 17:49:00 +00:00
fabric Requirements update (#18014) 2023-07-10 13:00:20 +00:00
pytorch Requirements update (#18014) 2023-07-10 13:00:20 +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 docs: fetch external sources (#17941) 2023-07-03 20:16:45 +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.