c6cbc3dcea
Update mlflow requirement in /requirements Updates the requirements on [mlflow](https://github.com/mlflow/mlflow) to permit the latest version. - [Release notes](https://github.com/mlflow/mlflow/releases) - [Changelog](https://github.com/mlflow/mlflow/blob/master/CHANGELOG.md) - [Commits](https://github.com/mlflow/mlflow/compare/1.0.0...v1.27.0) --- updated-dependencies: - dependency-name: mlflow dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| app | ||
| pytorch | ||
| README.md | ||
| base.txt | ||
| collect_env_details.py | ||
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[loggers], this list is stored in requirements/pytorch/loggers.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.