Hi! We’re considering migrating from a multi-repo setup (around 100 Python repos) to a monorepo using Pants, and I’d like to sanity-check our assumptions and get feedback. Current setup: • Single shared commons lib with lots of optional extras (previously multiple libs but it was hell) • Some repos are already monorepo-like, with multiple services that share env but deploy separately. • We also have an analyses monorepo, structured as:

libs/
  util_lib/
  other_lib/
analyses/
  analysis_a/
  analysis_b/

◦ Services (analyses) use

libs

via local dev = true in pyproject.toml ◦ Each analysis is opened individually in PyCharm as a standalone project with its own venv ◦ This works well for local dev: full IDE support, fast iteration ◦ One missing piece: no downstream test/lint triggered when shared libs change What I’m wondering: This analyses monorepo workflow feels like a simplified version of what Pants offers. Is that a reasonable assumption? Would Pants allow us to scale this model to all our services in a unified monorepo, while: • Preserving the local-isolated dev workflow? • Gaining downstream test/lint on shared lib changes? • Simplifying CI, avoiding dev = true hacks, and making dep graphs explicit? Thanks in advance for any insights!