tree c50af3117db041cb7b87266ee3b4847573a3ed69
parent 3271a8e50284e4302b72e2aeb58df513b07574e3
author Stefan Agner <stefan@agner.ch> 1718289863 +0200
committer GitHub <noreply@github.com> 1718289863 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmawXHCRC1aQ7uu5UhlAAACFsQAF8jQdOsklpnTLmVHzQHdyyL
 00fhuYOThWgi4iFpgoaaa2+6jLZbsrPome5hYIIW2e00D9wD7gpLThN0kHjMfWk5
 YFo2CeLHxDT06SPv1kMBbO2PKkj2iijnmPEPa2kznf7Na36pAmK1I+++EorXi77u
 mLtq6G0A+19Uj7DCg+G2/5S8SN2b97/rK8JxdNEwVVX7KyXEPg4hpd759frcO0iI
 rrZpR0q4qeeoG3HkiNbof47eh5cT9QyMS01huAGO0UJCSPpcEZkwwr4t2Of1gIUa
 XstxjyOoF/H7wAKO6RhQM8EPPRdvuGqfMnbhOoKnTtJD1cYxWVHzB2o5sobQSyi+
 h4+V4jRq8UHT7c/8chAfOMAmKCMRk9Rrtr4HaViQrhGMBDbTsWwbf86Ae3q2yUWJ
 nE+Sb+R6UctROq5MlWIbHHvqBPq1/o90yhLH0MKEC6u38q8wNt2TK/TOEk4TWNtV
 X7FgYeYglV+KYJk4V0taNVW+Vsd0U0kSuui9FMGBRvNX8V355VxgJCIHHAMc4M1F
 MfgnMxjFjKMnSDp9grY8kwdCPP1bpgmZrPP47tda7W1vCMFuWgtxB9+gAI46uf5N
 iIrf62HFveFgXdnfEm8bV94cJYAa0EmrHKY1lgWy+QlGjhOEfCQTDwcYHtY7Y2ZQ
 b1sszgS1zUqSy1cdZ14v
 =4iky
 -----END PGP SIGNATURE-----
 

[Python] Use thread-safe futures for concurrent operations (#33891)

* [Python] Use thread-safe futures for concurrent operations

Instead of using quasi-global variables in the ChipStack singleton
use device controller local futures to store results from callbacks.
This has several advantages, namely:
- Avoid unnecessary shared state between device controllers
- Avoid unnecessary shared state between various operations within a
  device controller (those who don't share callbacks could be called
  from different threads now)
- Explicitly set Futures to None to detect spurious/unexpected callbacks
- Better code readability
- concurrent.futures are thread-safe
- Will make asyncio transition easier

This change shouldn't change the external API.

* [Python] Fix EstablishPASESession API compatibility

* [Python] Make ConnectBLE behave as before