b1eceb1516
* bump: Torch `2.5.0`
* push docker
* docker
* 2.5.1 and mypy
* update USE_DISTRIBUTED=0 test
* also for pytorch lightning no distributed
* set USE_LIBUV=0 on windows
* try drop pickle warning
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* disable compiling update_metrics
* bump 2.2.x to bugfix
* disable also log in logger connector (also calls metric)
* more point release bumps
* remove unloved type ignore and print some more on exit
* update checkgroup
* minor versions
* shortened version in build-pl
* pytorch 2.4 is with python 3.11
* 2.1 and 2.3 without patch release
* for 2.4.1: docker with 3.11 test with 3.12
---------
Co-authored-by: Thomas Viehmann <tv.code@beamnet.de>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| _integrations | ||
| data | ||
| fabric | ||
| pytorch | ||
| README.md | ||
| ci.txt | ||
| collect_env_details.py | ||
| docs.txt | ||
| doctests.txt | ||
| typing.txt | ||
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.