- 
        Couldn't load subscription status. 
- Fork 88
Implicit discovery of entry points #346
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
Conversation
| A bit of context to the failed test on Ubuntu: Test only fail for  The reason test fail is because a change in behavior in the library  One solution to this problem that I have seen around, is to try: try:
    from importlib.metadata import entry_points
except ImportError:  # Python < 3.10 (backport)
    from importlib_metadata import entry_pointsHowever this does not work because  But I do not want to drop support/compat with Python 3.9, which is still one of the stable versions until 2025. FixFor now, I will add  some additional resources
 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to merge. Thanks!
| I just checked, and there are some (external) deprecation warnings for  | 
The following Pull Request:
pkg_resourcesand addsimportlib-metadataandimportlib-resources, which remain compatible with Python 3.9. In the near future (when Python 3.9 is no longer actively maintained), we can drop these new dependencies. In theory we should be able to replace them withimportlib.metadataandimportlib.resourceswith very minimal syntax changes (importlib is already included withinsetuptools`, but changed behavior starting with Python 3.10).Broadly,