lightning/requirements
awaelchli 4d6acda72e
Fix docs build (#19241)
2024-01-08 06:42:55 -05:00
..
_integrations Update Habana integration to 1.2 (#18877) 2023-10-26 19:08:50 -04:00
app Update traitlets requirement from <5.10.0,>=5.3.0 to >=5.3.0,<5.12.0 in /requirements (#18753) 2023-12-13 19:36:38 +01:00
data Make fsspec requirement the same across subpackages (#19085) 2023-11-29 10:36:28 -05:00
fabric Make fsspec requirement the same across subpackages (#19085) 2023-11-29 10:36:28 -05:00
pytorch Support 4bit BNB layers meta-device materialization (#19150) 2023-12-20 22:13:18 +01:00
store Bump coverage from 7.3.0 to 7.3.1 in /requirements (#18685) 2023-10-03 22:51:43 +02:00
README.md Remove devel.txt requirements file (#17466) 2023-04-25 07:21:21 +00:00
ci.txt ci: freeze requirements used in workflows (#19146) 2023-12-14 14:49:43 +01:00
collect_env_details.py docformatter: config with black (#18064) 2023-08-09 10:44:20 -04:00
docs.txt Fix docs build (#19241) 2024-01-08 06:42:55 -05:00
typing.txt Bump torch from 2.0.1 to 2.1.0 in /requirements (#18752) 2023-10-24 14:11:54 +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.