Add micropipenv #1523
Open
Add micropipenv #1523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this Python project?
A single Python script that is capable of installing Python packages into environment, primarily designed for containerized Python applications, but not limited to them.
What's the difference between this Python project and similar ones?
micropipenv supports all the well-known locking formats as used by pip-tools, Poetry or Pipenv. It is designed to be a single Python script with one optional dependency that is installing dependencies out of lock files without a need to install or distribute Poetry or Pipenv. Suitable for containerized Python applications where the overall image size and shipped software in the container image matters.
Why should I use micropipenv?
I would like to have a tool that "rules them all" - one lightweight tool to support all Python dependency lock file managers (pip-tools, Poetry, Pipenv) and lets users decide what they want to use when deploying Python applications in containerized environments (e.g. Kubernetes, ...)
I would like to have containerized Python applications as small as possible with minimum software shipped and required to build and run a Python application in production.
I would like to convert files produced by Pipenv/Poetry to a pip-tools compatible output.
I don't want to install Pipenv/Poetry, but I would like to run a project that uses Pipenv/Poetry for dependency management (e.g. restricted environments).
My Pipenv installation is broken and Pipenv upstream did not issue any new Pipenv release.
I would like to deploy my application into a production environment and my application dependencies are managed by Pipenv/Poetry (dependencies are already resolved), but I don't want to run Pipenv/Poetry in production.
See README file or project description on PyPI for more enumerated comparison and key features.