stop the interaction of hypothesis and disttrial from hanging the tests

[glyph]

something that disttrial is doing is making it so that a threading.local() reference being kept by a recursive hypothesis strategy (but only if it is actually recursive!) retained at module scope getting torn down during interpreter finalization prevents both workertrial and the parent disttrial processes from exiting, hanging forever

[glyph]

see also python/cpython#28525

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (76a2db0) 99.04% compared to head (91a5d73) 99.04%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #571   +/-   ##
=======================================
  Coverage   99.04%   99.04%           
=======================================
  Files          44       44           
  Lines        3883     3887    +4     
  Branches      519      520    +1     
=======================================
+ Hits         3846     3850    +4     
  Misses         23       23           
  Partials       14       14           

Impacted Files	Coverage Δ
src/klein/test/test_plating.py	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[adiroiban]

Hi.
I have close to zero experience with hypothesis.

But I guess the changes are fine and this can be merged.

Thanks!

[exarkun]

Another reference - HypothesisWorks/hypothesis#3585

[glyph]

@exarkun does that reference tell us when we can remove this gross hack? :)

[exarkun]

@exarkun does that reference tell us when we can remove this gross hack? :)

This comment seems to suggest the fix will be in the next bugfix release of Python 3.11 and the next major release. There is also an upstream bug report which is closed now (and seems like a duplicate of the cpython bug report linked here, above).

[glyph]

@exarkun does that reference tell us when we can remove this gross hack? :)

This comment seems to suggest the fix will be in the next bugfix release of Python 3.11 and the next major release. There is also an upstream bug report which is closed now (and seems like a duplicate of the cpython bug report linked here, above).

Thanks for those references!