]> git.ipfire.org Git - thirdparty/fastapi/fastapi.git/commit
:fire: Remove Pipfile.lock from the repository (each contributor can keep his/her...
authorSebastián Ramírez <tiangolo@gmail.com>
Thu, 27 Jun 2019 19:51:38 +0000 (21:51 +0200)
committerGitHub <noreply@github.com>
Thu, 27 Jun 2019 19:51:38 +0000 (21:51 +0200)
commitea9277aab4f8652d3bdecb7da5df4e022c5c03a8
tree00c8efe2a634cf5d3014ee0ebfe79d1d5549d95f
parent8d86fca0273ca3108220c7be7c5c5a3ba5c8fa80
:fire: Remove Pipfile.lock from the repository (each contributor can keep his/her locally)

* :fire: Remove Pipfile.lock

Being a library, it should work independent of locking of dependency tree.

The Pipfile (and Pipfile.lock) is only used locally for development of FastAPI itself, it doesn't affect final users (that is controlled with pyproject.toml).

The Pipfile.lock adds unnecessary noise to PRs that update/upgrade development packages, and the locking is not the same in all environments (e.g. Linux, Mac, and Windows).

Each FastAPI contributor (developing FastAPI itself) can have his/her own Pipfile.lock, but it doesn't have to be in git.

* :see_no_evil: Add Pipfile.lock to .gitignore
.gitignore
Pipfile.lock [deleted file]