Page 1 of 1

CircuitPython project management, libraries breaking between projects

Posted: Thu Jul 02, 2026 11:00 pm
by sam_python
Three CircuitPython boards on my desk. Project A needs adafruit_sensor 5.x, project B needs 4.x. Different builds break each other.

From Python web world, I would use venv. CircuitPython does not have that.

Options found:
  • Per-board lib copy (manage manually, error-prone)
  • Circup tool (manages libraries per board, version-pinning weak)
  • Git submodule each project (heavy)
CircuitPython community: how do you manage multiple projects with conflicting lib requirements? Or is this just not a thing because each board lives one purpose?