Skip to main content

PipFlow

Background

Pipflow is built for developers who deploy their Python software using Docker and Cloud Native technologies. When building docker images our constraints are:

  • The more slim the image, the better.
  • The less image layers, the better.
  • Don't reinvent the wheel by installing a new package manager in your Dockerfile. These tools tend to use lock files, which are fine in general, but in Docker they are redundant because we already have a way to pin dependencies: Docker image layers.

This leave us with one option: Continue to use plain old pip, but create some new workflows that improve the developer experience.

For example, Pipflow replaces this workflow:

$ pip3 install <new-package>
$ pip3 freeze | grep <new-package> >> requirements.txt
$ docker build ... # (A redudant install)

with this:

$ pipflow add <package>

Setup

Install pipflow on your HOST OS only (macOS, Windows, Linux etc). Do not add Pipflow to your requirements.txt.

pip3 install pipflow

Usage

Add a new package

pipflow add <package-name>

Remove a package

pipflow remove <package-name>

Upgrade a package version

pipflow upgrade <package-name>

Upgrade all packages

pipflow upgrade-all

Vew all packages eligible for upgrade

pipflow view-all

License

MIT Copyright (c) 2021 Michael.

Metadata

Release files for Pipflow 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Pipflow 0.1.2
File Size Uploaded Provenance
Pipflow-0.1.2.tar.gz 4.5 kB Without provenance Details

Release files / Pipflow-0.1.2.tar.gz

Download URL Pipflow-0.1.2.tar.gz
Size 4.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e40b1d73d0ec25876038b4c0daaeedc21c7a662200ca1d9f942f95817f670110
BLAKE2b-256 checksum
How to use checksums
d5d6177d71a6597b571b0bfe70530d70a331e705e85a7f2d0115556ffd090681
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.0

Security for Pipflow 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page