lightning/requirements
Justus Schock 1cee84ca2d
Replace LightningClient with import from lightning_cloud (#18544)
2023-09-13 14:55:05 +02:00
..
_integrations Support true 16-bit precision with deepspeed in Trainer (#18217) 2023-08-08 14:07:25 -04:00
app Replace LightningClient with import from lightning_cloud (#18544) 2023-09-13 14:55:05 +02:00
data replace tests skip with soft xfail (#18486) 2023-09-12 23:11:03 +02:00
fabric replace tests skip with soft xfail (#18486) 2023-09-12 23:11:03 +02:00
pytorch replace tests skip with soft xfail (#18486) 2023-09-12 23:11:03 +02:00
store replace tests skip with soft xfail (#18486) 2023-09-12 23:11:03 +02:00
README.md Remove devel.txt requirements file (#17466) 2023-04-25 07:21:21 +00:00
collect_env_details.py docformatter: config with black (#18064) 2023-08-09 10:44:20 -04:00
docs.txt Bump sphinx-toolbox from 3.4.0 to 3.5.0 in /requirements (#18409) 2023-08-30 05:34:13 -04:00
typing.txt Bump mypy from 1.4.1 to 1.5.1 in /requirements (#18347) 2023-08-21 11:40:29 +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.