fix: add setuptools python_requires check

[Nicusor97]

Note: supporting python_requires requires setuptools>=24.2.0 and pip>=9.0.0 to benefit from it.
Details here: https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires

Will prevent users with Python 2.7 or 3.5 from downloading a sdist version they cannot build.

I see two problems:

• seems like you dropped the Python 2 support by adding https://github.com/pytest-dev/pytest-timeout/blob/master/setup.py#L4. If you will try to build this on python 2 you will get this error: 'encoding' is an invalid keyword argument for this function
• The pytest version has been upgraded to the latest from what I can see in the setup.py https://github.com/pytest-dev/pytest-timeout/blob/master/setup.py#L19 and starting from the 5.0.0 version, pytest dropped the Python 2 support.

From my point of view, both cases will be fixed by adding python_requires>=3.6 the same as pytest: https://github.com/pytest-dev/pytest/blob/main/setup.cfg#L54

(I'm not sure if the changelog should be updated in the same PR, if yes I will do it in another commit)

[graingert]

also will need to yank v2.0.0

[Nicusor97]

@graingert Yes, the v2.0.0 must be yanked.

[graingert]

python_requires requires setuptools>=24.2.0 and pip>=9.0.0 to benefit from it.

pytest-timeout ships a wheel so should be fine

[Nicusor97]

@graingert Do you know if the issues that I have with the jobs on Python 3.6 and 3.9 were there before my changes ?

[graingert]

@graingert Do you know if the issues that I have with the jobs on Python 3.6 and 3.9 were there before my changes ?

3.6 could be related to coverage v6.0.1

[graingert]

yep 3.6 failures predate this PR #102 (comment)

I fixed the 3.9 linting error

[Nicusor97]

Ah, you are right, Thanks for fixing the py3.9 jobs. 😄

[Nicusor97]

I closed it by mistake. When the PR will be approved I think a new version should be released and v2.0.0 yanked

[Nicusor97]

We need one more approval from one of the maintainers in order to merge this fix. Can someone take a look and also help with releasing a new version (also don't forget to yank the v2.0.0 version).

[henryiii]

@RonnyPfannschmidt perhaps?

[RonnyPfannschmidt]

I can approve, but I don't have any bandwidth for unfamiliar releases until the end of the week

[flub]

if in doubt, always update the changelog in the same PR :)

[flub]

2.0.1 released, 2.0.0 yanked

This is a good time to promote: if someone can do a better job than me maintaining pytest-timeout please do so! all you have to do is ask.

[graingert]

@flub thanks for the release and the yank!

[graingert]

if in doubt, always update the changelog in the same PR :)

If every PR includes a changelog change then all PRs will conflict, something like towncrier can help here

[flub]

if in doubt, always update the changelog in the same PR :)

If every PR includes a changelog change then all PRs will conflict, something like towncrier can help here

Yeah, true. But this isn't exactly a super busy project... I'm rather for keeping things simple if possible.