> But not for a specific warning, what I tried to do here.  But OK, maybe it is not that important to do it (the reason I wanted to do that was to avoid unrelated failures, eg when numpy starts raising a warning on something unrelated used under the hood).    sure, but try to guard against *unexpected* warnings is a bit of a rabbit hole