We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Python monorepos: what, why and how

Formal Metadata

Title
Python monorepos: what, why and how
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
As organizations and repos grow, we have to choose how to manage codebases in a scalable way. We have two architectural alternatives: Multirepo: split the codebase into increasing numbers of small repos, along team or project boundaries. Monorepo: Maintain one large repository containing code for many projects and libraries, with multiple teams collaborating across it. In this talk we'll discuss the advantages of monorepos for Python codebases, and the kinds of tooling and processes we can use to make working in a Python monorepo effective. At the end of this talk you will understand the tradeoffs of different codebase architecture choices, and how to evaluate tooling and processes that keep your repo humming along at scale. No prior knowledge is required.