You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to remove the dependency on importlib_metadata in Python 3.10+, but Twine will still need it for as long as it supports older versions of Python. So, I think it's worth weighing the complexity of conditional imports vs. an additional dependency.
I think this should at least wait until 3.10 is officially released and is added to Twine's testing matrix. If we do decide to use importlib.metadata, then I think the version check should be done in one place, as suggested in #772 (comment).
The text was updated successfully, but these errors were encountered:
The use of importlib_metadata relies on features that were introduced in
python 3.10. Aside for that, it should be fine to use the stdlib
directly.
Fixespypa#773
Follow-up to #772 (review) and #732 (comment).
It'd be nice to remove the dependency on
importlib_metadata
in Python 3.10+, but Twine will still need it for as long as it supports older versions of Python. So, I think it's worth weighing the complexity of conditional imports vs. an additional dependency.I think this should at least wait until 3.10 is officially released and is added to Twine's testing matrix. If we do decide to use
importlib.metadata
, then I think the version check should be done in one place, as suggested in #772 (comment).The text was updated successfully, but these errors were encountered: