lightning/requirements
Jirka Borovec b19c3a961c
ci: pin `pytest` for package doctests (#19567)
2024-03-04 15:09:04 +01:00
..
_integrations Remove the Colossal AI integration (#19528) 2024-02-26 10:59:15 +01:00
app Bump Lightning Cloud 0.5.64 (#19372) 2024-01-30 14:57:11 +00:00
data migrate Data subpackage (#19523) 2024-02-26 08:25:00 -05:00
fabric Update mypy in CI (#19449) 2024-02-13 12:09:35 +01:00
pytorch `load_from_checkpoint` support for LightningCLI when using dependency injection (#18105) 2024-02-23 10:55:07 +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
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.