python Documentation

Technical Documentation: plotly/python

ℹ️ Provenance: Multi-Tier Ingestion · CodeWiki Reference

Overview (`README.md`) Copy Section

Python Paketo Buildpack

`gcr.io/paketo-buildpacks/python` Copy Chapter

The Python Paketo Buildpack provides a set of collaborating buildpacks to build a Python-based application
These buildpacks include:

• CPython CNB
• Pipenv CNB
• Pipenv Install CNB
• Pip CNB
• Pip Install CNB
• Miniconda CNB
• Conda Env Update CNB
• Poetry CNB
• Poetry Install CNB
• Poetry Run CNB
• Python Start CNB

Additionally, the following utility buildpacks are included for all application types

• CA Certificates CNB
• Watchexec CNB
• Procfile CNB
• Environment Variables CNB
• Image Labels CNB

The buildpack supports building simple Python applications or applications which
utilize either Conda,
Pipenv or Pip for
managing their dependencies.

Pipenv,
Pip,
or Poetry for managing their dependencies.

Build: Copy Chapter

./scripts/package.sh --version 5.1.1 --output quay.io/plotly/paketo-buildpacks-python:5.1.1

Check out the Python Paketo Buildpack docs for sample usage and more information.

The Python buildpack is compatible with the following builder(s):

• Paketo Jammy Full Builder
• Paketo Bionic Full Builder
• Paketo Jammy Base Builder
• Paketo Bionic Base Builder

Overview (`.github/README.md`) Copy Section

Python Paketo Buildpack

A copy of the upstream README.md can be found here: README.md

Plotly Branches

• The main-upstream branch of this repository is used to sync in the main branch of the upstream as its source. It does not contain any custom Plotly code changes
• The main branch of this repository is used to be the most up to date branch containing custom Plotly code changes
• The XY-release branches of this repository are made off of the main branch as part of our code freeze process: DE Release Guide

Plotly Release Flow

• All PRs (other than an upstream sync detailed below) should first land on main
• If a PR is needed for a given release, a new PR should be made against that release branch
• When needing to pull in upstream changes (typically done as a post-release task to stay up to date as needed):
  • Navigate the the main-upstream branch
  • Select Sync fork
  • A PR should then be opened to add these changes to our main branch, favouring our custom work whenever there are conflicts

--- METRICS ---

• Files Extracted: 2
• Estimated Token Budget: ~971 tokens
• Canonical Reference: https://codewiki.google/github.com/plotly/python