How cocotb made Python-powered verification mainstream -- and what comes next
summary
cocotb now ships 250 prebuilt wheels (simulator × Python × platform) so users no longer compile C++ at install time, and CI runs publicly against Questa, Riviera‑Pro and Xcelium to catch regressions. Ongoing work includes deprecations and breaking changes—most notably the .value return type change (BinaryValue → logical type) and tightened fork/ coroutine semantics—plus a Python test‑runner to replace fragile Makefile flows. Mixed‑simulator or mixed‑language emulation remains unresolved; expect concrete migration steps and API churn.
AI-written summary · about
chapters (12)
- 0:00cocotb’s journey
- 1:02What is cocotb
- 4:32Industry adoption
- 6:39Python and cocotb match
- 7:42Open-source challenges
- 9:08Installing cocotb
- 10:55Automated simulator testing
- 12:39Cleaning cocotb APIs
- 14:25Future updates
- 16:36Beyond Makefiles
- 17:41Community opportunities
- 18:45Q&A
