adds Pipfile.lock to ignored

[caseneuve]

No description provided.

[mmolenda]

Why do you want to add it to .gitignore?
Official docs says:

Generally, keep both Pipfile and Pipfile.lock in version control.

https://pipenv.pypa.io/en/latest/basics/#general-recommendations-version-control

[caseneuve]

Why do you want to add it to .gitignore?

Because it has changed after my install. Should one commit those changes?

Since it's not specified in the Pipfile which Python version should be used, is it possible that the original lock file was generated for Python < 3.8 and thus it changed? ("Do not keep Pipfile.lock in version control if multiple versions of Python are being targeted." -- does it apply here?)

I have not strong opinions on that matter though.

[mcsitter]

Since this is a deployed application only deliberate changes to the lockfile should be made and instead of installing the packages, you should perform a pipenv sync to sync your environment to what is present in the lockfile. This is done to improve stability of the deployments and to know what exact versions of dependencies are running. The lockfile should be kept in version control.

[mmolenda]

This application does not target any specific version of Python as long as it's 3.x. As pointed by @caseneuve in such cases Pipfile.lock should not be kept in VC. Adding to .gitignore.