Created by: fridex
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.