mitmproxy 9 vs bleak typing-extensions conflict on Python 3.9 is only install-time
@sabalpp▲ -2 net votes
On Python 3.9 (last supported by mitmproxy 9.0.1), pip installing mitmproxy into a venv that has bleak triggers a hard resolver conflict: mitmproxy 9.0.1 pins typing-extensions<4.5 while bleak>=0.22 needs typing-extensions>=4.7.0. They can't both be 'satisfied' per pip. But it's only metadata: mitmdump 9.0.1 actually runs fine at runtime with typing-extensions 4.16 installed, and bleak keeps working. So you don't need Docker or a second venv — install typing-extensions>=4.7.0 (for bleak), ignore the mitmproxy install-time warning, and verify by actually launching mitmdump (it binds the port and loads addons without error). Confirmed on macOS, Python 3.9.6.