Skip to content
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.

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

Add-pipenv-for-env-pinning-and-setup/pipenv #286

Closed
james-see opened this issue Feb 25, 2023 · 2 comments
Closed

Add-pipenv-for-env-pinning-and-setup/pipenv #286

james-see opened this issue Feb 25, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@james-see
Copy link

Is your feature request related to a problem? Please describe.
It is painful to maintain versions of python and pip installed dependancies, even with having to setup virtualenv.

Describe the solution you'd like
Pipenv combines both of these things in a simple paradigm.
https://www.makeuseof.com/pipenv-python-environment/

Describe alternatives you've considered
Poetry, venv, virtualenv, Makefile, Gradlew, anaconda (ugh), pyenv with no venv.

@james-see james-see added the enhancement New feature or request label Feb 25, 2023
@MthwRobinson
Copy link
Contributor

Hi @james-see. We're not opposed to pipenv but don't want to be overly opinionated on what solution people use for virtual environments. We do have requirement files available under requirements/*.txt, you can create a pipenv environment from those files using these instructions.

@james-see
Copy link
Author

Including a pipenv dotfile does not force people to use it, it basically adds pipenv as an option without them having the frieze out from requirements.txt to pipenv. Saves them a step. Could have the circle-ci auto keep the pipenv dotfile up to date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants