Activity

1. emmatyping commented on Sep 1, 2017

   

   emmatyping

   on Sep 1, 2017

   Member

   More actions

   You probably want to use –ignore-missing-imports or one of the more relaxed options specified here: https://mypy.readthedocs.io/en/latest/command_line.html#following-imports-or-not

   That will cause Mypy to not raise errors if it doesn't find stubs for the modules.

   Reacted by Vincenzo Ferrari, Andrew Martin, Pranay Aryal, Martin Thoma, Lukas N.P. Egger, Vishes, Viacheslav Artemchuk, Samuel Carlsson, George J. J. Wu, Jizong's Fox and 21 more

   Reacted by gmanka and Jacob-Brink
2. henryJack commented on Sep 1, 2017

   

   henryJack

   on Sep 1, 2017

   Author

   More actions

   Ah, So sorry. I thought I tried that!

   Yep, that switch works perfectly, thanks for the fantastic tool!
3. henryJack

   closed this as completedon Sep 1, 2017
4. boompig commented on Jan 16, 2018

   

   boompig

   on Jan 16, 2018

   More actions

   Is this the only way to suppress this warning?

   The documentation for --ignore-missing imports states:

   --ignore-missing-imports suppresses error messages about imports that cannot be resolved (see Following imports or not? for some examples).

   This seems extremely broad, as (I believe) this also squelches errors on import foo when module foo does not exist (not just that it has no stub file). Although to be honest I'm new to mypy so I might have misinterpreted what this means. What about a flag to suppress the absence of stub files for selected modules that are known to not have stub files?

   Example usage: --ignore-missing-stubs=foo,bar,baz. Or specify this explicitly in a config file.

   Currently, a large number of python modules lack stub files, so having a way to surgically suppress this warning would be extremely helpful, especially in automated builds.

   Reacted by laike9m, Hiroaki Ogasawara, Josiah, Shun Kakinoki, Jirka Daněk, Tyler Couto, Antonino Ingargiola, Max Kühn, James Ostrander, Manuel Vonthron and 16 more
5. gvanrossum commented on Jan 16, 2018

   

   gvanrossum

   on Jan 16, 2018

   Member

   More actions

   Yeah, an extra flag could help here. Do you want to help adding it by submitting a PR?
6. boompig commented on Jan 18, 2018

   

   boompig

   on Jan 18, 2018

   More actions

   Let me give this a try.
7. boompig

   added 2 commits that reference this issue on Jan 18, 2018

   Added --ignore-missing-stubs flag

   b496ee4

   Added --ignore-missing-stubs flag

   899240d
8. lingz commented on Sep 13, 2018

   

   lingz

   on Sep 13, 2018

   More actions

   We didn't use the hammer option of total ignoring imports, because warnings about modules that didn't exist was great for CI. So we ended up suppressing stub warnings one by one with our mypy.ini file, like the following:

   mypy.ini

   [mypy-tornado.*]
   ignore_missing_imports = True
   
   [mypy-pandas.*]
   ignore_missing_imports = True
   
   [mypy-numpy.*]
   ignore_missing_imports = True
   
   [mypy-sklearn.*]
   ignore_missing_imports = True
   
   [mypy-matplotlib.*]
   ignore_missing_imports = True
   
   [mypy-scipy.*]
   ignore_missing_imports = True
   

   We run mypy --config-file=../mypy.ini ./**/*.py to type check, following imports as per normal.

   Reacted by Mateusz Legięcki, laike9m, Daniel Vianna, Vishes, Samuel Carlsson, Viacheslav Artemchuk, Aru Sahni, rodrigodc, Vladimir Jimenez, Jirka Daněk and 27 more

   Reacted by Jorge Leitao, Joe Osborn, Jirka Daněk, mishudark, Shuvo Saha, Konstantin Manna, gmanka and Mateusz Głowiński
9. henryJack commented on Sep 14, 2018

   

   henryJack

   on Sep 14, 2018

   Author

   More actions

   @boompig - To add to @lingz nice example... You can find more information about the current module specific settings in the per module flags section in the docs.
10. teto

    added a commit that references this issue on Oct 31, 2018

    mypy: fix "No library stub file for module XXXXXX"

    f8ee3f0
11. stuaxo commented on Feb 3, 2020

    

    stuaxo

    on Feb 3, 2020

    More actions

    It would be great if there was some way of specifying a requirements file as a source for packages to ignore.
12. thejaminator commented on Jan 3, 2023

    

    thejaminator

    on Jan 3, 2023

    More actions

    It seems sad that #4491 got closed.

    It can be very annoying to have to whitelist so many dependencies in your codebase.

    Another way is to simply override the setting for your own codebase.
    That way, your own codebase's imports gets typechecked.

    i.e.

    [mypy]
    ignore_missing_imports = True
    
    # where api_folder is your source code
    [mypy-api_folder.*]
    ignore_missing_imports = False
    

    Reacted by John Chavez, Gunni, danuo and Mikhail Gasanov