Dev PI: The Tool You Never Knew You Needed
summary
Offline development at summer camp leads to a concrete setup: run devpi as a local PyPI proxy on a laptop, point pip.conf to it, then warm its cache by cloning Twisted and running tox across many envs so thousands of package files are cached locally. Use separate devpi indexes for private upload testing of packages, and chain the laptop devpi to a team devpi so proprietary and cached public packages resolve reliably when reconnecting.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:21Acknowledgement of Country
- 0:38Camp Tawonga
- 1:25Working Without Connectivity
- 2:41Bringing Up Server
- 3:54Temporary Default
- 4:16Permanent Default
- 4:48Warm Cache, Cold Network
- 6:04A Private Area
- 6:52Experimenting
- 7:44A Daisy Chain
- 8:07Parting Thoughts
related talks
31mDevpi for teams
37mAutomated deployment of Python packages for development
30mBootstrapping Your Local Python Environment
22mBuilding towards a holistic development service — Amjad Masad
41mTaming the toxic python environment on your laptop
02h 25mModern Python Developer's Toolkit
38mBootstrapping your Local Python Environment
02h 36mPython Packaging Demystified