-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Python 3.7 (up to 3.9?) support #275
Comments
Seems IoT Lab won't be updating soon; users can use own Python installations instead. By now,
so in the next go I'll probably even drop 3.9 support as well. Python 3.10 has some interesting stuff, but off my head there aren't any places in the code that would profit from structural pattern matching. aiter and anext could be helpful for readability (but don't allow big simplifications), and there are no major enhancements in asyncio, socket, urllib or other networking related stuff -- it'll just trim down the test matrix. |
Updated report given riotdocker will update sooner this time:
Which means PyPy becomes the critical component against a 3.11 upgrade (but then again, 3.11 primarily enhances typing, and while toml is attractive for transport descriptions, it's also available as an external module) |
The next round of Python required-version bumps is not too promising in terms of new features, but there are some:
None of the other changes appear to be very helpful to aiocoap (or they are, but are automatically useful to users of the new version, or are useful already by being in any version like the stabilization of
asyncio.run
); so it would seem that the earliest Python 3.7 removal is due is when dependencies start becoming hard to get by on that platform, when the CI images generally become problematic, or when the CI list of platforms is just getting too long.Still, I'd like to check which user groups have concrete timelines:
As outlined above, I'm in no hurry to bump the Python dependency, but if anyone needs aiocoap supporting 3.8 for longer than any of those listed, please speak up.
The text was updated successfully, but these errors were encountered: