Closed exarkun closed 3 years ago
@exarkun See this PR: https://github.com/pytest-dev/pytest-timeout/pull/103 It should fix the issue that you spotted.
Same thing hit on pybind11 - I'd rather not have to mess with our Python 2 CI, hoping to leave it alone until we drop it at the end of the year. Thanks for the PR and looking forward to the yank! :heart:
Compare with installation log from prior to 2.0.0 release:
I don't know if pytest-timeout cares to continue supporting Python 2 in new releases (from the metadata, I guess not) but it would be considerate if the project set its metadata correctly so that Python 2 installations could find the last Python 2-supporting release automatically instead of trying to use a Python 3-only release.