Skip to content
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

Relies on legacy API of importlib.resources #170

Closed
jaraco opened this issue Oct 17, 2021 · 1 comment
Closed

Relies on legacy API of importlib.resources #170

jaraco opened this issue Oct 17, 2021 · 1 comment

Comments

@jaraco
Copy link

jaraco commented Oct 17, 2021

The project relies on an interface in importlib resources that's marked as legacy and slated for removal. Better would be to rely on the preferred files() API (requires importlib_resources on Python<3.9).

@sigmavirus24
Copy link
Member

As mentioned in #147 until importlib.* can actually really once-and-for-all stabilize to a good place with a backport that won't cause us headaches when people use this in an environment with a package with different version constraints on the backport, we won't be upgrading from those deprecated APIs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants