Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A awesome-python
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 317
    • Merge requests 317
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Vinta Chen
  • awesome-python
  • Merge requests
  • !1523

Add micropipenv

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Administrator requested to merge github/fork/fridex/micropipenv into master 5 years ago
  • Overview 1
  • Commits 1
  • Pipelines 1
  • Changes 1

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.

Activity

  • Loading
  • Loading
Please register or sign in to reply
Status
Pipeline
Triggerer
Stages
Actions

2 years ago

Add micropipenv
#856
github/fork/fridex/micropipenv 3177ce5e
latest Auto DevOps
avatar
0 Assignees
None
Assign to
0 Reviewers
None
Request review from
Labels
2
Client: Python Enhancement: General
2
Client: Python Enhancement: General
    Assign labels
  • Manage project labels

Milestone
4.2.0
4.2.0 (expired)
None
Time tracking
No estimate or time spent
Lock merge request
Unlocked
0
0 participants
Reference: OpenAPITools/openapi-generator!4163
Source branch: github/fork/fridex/micropipenv

Menu

Explore Projects Groups Snippets