Yes, I figured if all the function calls under Application.quit pass, but maybe a subprocess or thread is misbehaving, a "raise SystemExit(0)" at the end might force a quit – and if sailfish-qml/qmlscene/qml is waiting for Python, then the whole app process tree might quit, maybe.

For what it's worth, I did test http.pool.terminate with online providers in different connection states and it seemed to work fine, but it's possible I missed something or OSM Scout behaves differently. Also, if there's a problem in the http module, one solution would be to just swap it for requests (plus its dependencies). I was reluctant to bundle stuff, but I also think I underestimated the difficulty of writing a custom HTTP connection pool, there's been various corner case issues.