Rooba
/
lightning
mirror of https://github.com/Lightning-AI/lightning.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
lightning/requirements
History
Sherin Thomas 7cbdc68449
[App] Cold start proxy in autoscaler (#16094) 
* cold start proxy

* Update src/lightning_app/components/serve/auto_scaler.py

* changelog

* better-doc

Co-authored-by: Akihiro Nitta <nitta@akihironitta.com>
Co-authored-by: thomas chaton <thomas@grid.ai>
Co-authored-by: Jirka Borovec <6035284+Borda@users.noreply.github.com>
 		2022-12-20 09:47:10 +00:00
..
app [App] Cold start proxy in autoscaler (#16094) 2022-12-20 09:47:10 +00:00
lite Update torchvision requirement from <=0.14.0,>=0.11.1 to >=0.11.1,<0.15.0 in /requirements (#16108) 2022-12-19 16:52:55 +00:00
pytorch Update scikit-learn requirement from <1.1.3,>0.22.1 to >0.22.1,<1.2.1 in /requirements (#16107) 2022-12-20 05:21:02 +00:00
README.md Remove examples and loggers from develop dependencies (#15282) 2022-10-25 09:23:26 -04:00
collect_env_details.py Update collect env details and issue template (#14017) 2022-08-10 00:38:18 +00:00
docs.txt Update myst-parser requirement from <0.17,>=0.15 to ==0.18.1 in /requirements (#14417) 2022-11-09 18:55:16 +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. The only exceptional requirement file is devel.txt, which aggregated all the needed requirements for development.

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.