gh-100522 Add a test for 'futures.as_completed' timing out with a non-zero timeout value

[JosephSBoyle]

Resolves a longstanding TODO in the futures tests:

TODO([email protected]): Should have a test with a non-zero timeout.

by fixturizing the existing test.

• Issue: Resolve TODO comments in test_concurrent_futures.py #100522

[JosephSBoyle]

@gpshead bump:)

[JosephSBoyle]

@gpshead bump

[AlexWaygood]

Thanks for your interest in contributing, @JosephSBoyle, it's great to see :)

Unfortunately, CPython is mostly run by volunteers; very few people are paid full-time to work on CPython itself. Added to this, many CPython devs are juggling their free time between this repo and other open-source projects.

Pinging a reviewer if you haven't had a response after a few weeks is absolutely fine, but repeatedly pinging every few days isn't. Please try to be respectful of other people's time :)

[JosephSBoyle]

Hi @AlexWaygood, thanks for your message. I understand what you're saying about devs being largely volunteers with other responsibilities. Apologies if I was being impolite with my bump comments, that certainly wasn't my intention.

[AlexWaygood]

No worries at all @JosephSBoyle — just something to bear in mind for the future :)

[JosephSBoyle]

Thank you for the review and merge @gpshead:)