-
Notifications
You must be signed in to change notification settings - Fork 30
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
support suppression of warning on import
#30
Comments
I have bumped into this when migrating some code that is using |
I was able to use the warning message matching for this:
|
@ghik should this be closed, then? |
@SethTisue why? It's as unsolved as it was in the beginning so it still serves its original "partly documentation" purpose, right? |
I wasn't aware when I opened the ticket that |
Yeah, but it's global so it can't be used to silent each import independently. |
Unfortunately this suppressed all warnings |
@taig |
@ghik I prepared a reproducer and checked out the project to take a deeper look and possibly submit a fix. I'm happy to share the reproduction repo and raise a new issue but I have a couple assumptions that I'd like to clarify beforehand:
|
#42 is fixed and IMO this is the best solution for suppressing unused import warnings. |
typically the warning would be a deprecation warning
imports can't have annotations, so it would have to be via some other mechanism:
(opening the issue partly as documentation that there isn't any support currently)
The text was updated successfully, but these errors were encountered: