lightning/requirements
Jirka Borovec 0fb267b427
docs: use fixed version of adjust links to 'stable' (#19697)
2024-03-27 07:11:48 +01:00
..
_integrations Remove the Colossal AI integration (#19528) 2024-02-26 10:59:15 +01:00
app docs: pin version in links to external docs [1/n] (#19584) 2024-03-19 16:35:40 +01:00
data migrate Data subpackage (#19523) 2024-02-26 08:25:00 -05:00
fabric ci: bump torch to `2.2.1` (#19687) 2024-03-22 21:56:22 -04:00
pytorch ci: bump torch to `2.2.1` (#19687) 2024-03-22 21:56:22 -04:00
store
README.md
ci.txt ci: freeze requirements used in workflows (#19146) 2023-12-14 14:49:43 +01:00
collect_env_details.py
docs.txt docs: use fixed version of adjust links to 'stable' (#19697) 2024-03-27 07:11:48 +01:00
doctests.txt ci: pin `pytest` for package doctests (#19567) 2024-03-04 15:09:04 +01:00
typing.txt Update mypy in CI (#19449) 2024-02-13 12:09:35 +01: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.