Skip to content

Conversation

@joshuarli
Copy link
Contributor

I briefly attempted to port usage of imp over in #449, but it turned out to be nontrivial.

In the future you'll want to either finish the port, or restrict python versions to whenever imp will be removed.

@brianmay
Copy link
Member

brianmay commented Jun 9, 2020

I think this needs a proper fix. I don't think hiding a deprecation warning is the proper fix, it will come around and bite as at a latter date.

Sorry, I have no idea how to fix this though, and don't have time to think about it right now.

@joshuarli
Copy link
Contributor Author

Sure, I can take another look at #449 sometime soon.

FWIW, I haven't heard anything about imp removal in Python 3.9, it'll probably still stick around for a while. There's also the path of vendoring imp, which is probably not that bad, but hopefully I or someone else can figure out a better way.

@joshuarli joshuarli closed this Jun 9, 2020
@joshuarli joshuarli deleted the chore/ignore-imp-deprecation-warning branch June 9, 2020 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants