Declare Python 3.10 support deprecated.#5183
Conversation
No obvious way to add a warning with pyproject.toml like we used to do with setup.py?
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5183 +/- ##
==========================================
+ Coverage 85.51% 86.38% +0.87%
==========================================
Files 282 282
Lines 59489 59489
==========================================
+ Hits 50871 51389 +518
+ Misses 8618 8100 -518 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@peterjc I don't think there is a way to raise a DeprecationWarning on install with You could but it into However, I would argue since python 3.10 reaches EOL this year, users should expect deprecation. Furthermore, if users continue to use python 3.10 and have no upper bound on their |
|
Thanks, I agree while it would be a nice to have a warning for our users, it is hardly going to be a surprise given this is driven by the Python 3.10 EOL. |
No obvious way to add a warning with
pyproject.tomllike we used to do withsetup.py? CC @xelanderntI hereby agree to dual licence this and any previous contributions under both
the Biopython License Agreement AND the BSD 3-Clause License.
I have read the
CONTRIBUTING.rstfile, have runpre-commitlocally, and understand that continuous integration checks will be used to
confirm the Biopython unit tests and style checks pass with these changes.
I have added my name to the alphabetical contributors listings in the files
NEWS.rstandCONTRIB.rstas part of this pull request, am listedalready, or do not wish to be listed. (This acknowledgement is optional.)