New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pipenv Usage #5

Open

OpenSourceIronman opened this issue Apr 8, 2020 · 1 comment

Labels

Contributor

OpenSourceIronman commented Apr 8, 2020

General Recommendations & Version Control

Generally, keep both Pipfile and Pipfile.lock in version control.
Do not keep Pipfile.lock in version control if multiple versions of Python are being targeted.
Specify your target Python version in your Pipfile’s [requires] section. Ideally, you should only have one target Python version, as this is a deployment tool. python_version should be in the format X.Y and python_full_version should be in X.Y.Z format.

Since we are targeting just Python 3.8 we will be keeping Pipfile and Pipfile.lock in version control.
https://pipenv.readthedocs.io/en/latest/basics/

OpenSourceIronman added the documentation label

Collaborator

dull7295 commented May 20, 2020

MURALI will give a demo when time permits to the team on best practices about pip files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment