Make it possible to use local stubs #25

Activity

1. ashleyh commented on Dec 13, 2012

   

   ashleyh

   on Dec 13, 2012

   Contributor

   More actions

   I wonder if it would be better to be able to specify additional stubs dirs as a command line argument or something...
2. JukkaL commented on Dec 13, 2012

   

   JukkaL

   on Dec 13, 2012

   CollaboratorAuthor

   More actions

   You can specify an additional module path (for looking up stubs or any modules) by using the MYPYPATH environment variable. The implicit 'stubs' directory would just be a convenience.
3. JukkaL

   removed

   python semantics

   on Jul 25, 2014
4. JukkaL

   added

   priority

   on Nov 21, 2014
5. JukkaL commented on Dec 8, 2014

   

   JukkaL

   on Dec 8, 2014

   CollaboratorAuthor

   More actions

   As we now have an alternative extension for stubs, this is no longer as urgent: #345
6. JukkaL

   removed

   priority

   on Dec 21, 2014
7. JukkaL commented on May 17, 2015

   

   JukkaL

   on May 17, 2015

   CollaboratorAuthor

   More actions

   The .pyi extension seems to address this issue, so closing this now.
8. JukkaL

   closed this as completedon May 17, 2015
9. DionysusG commented on May 31, 2016

   

   DionysusG

   on May 31, 2016

   Last edited by DionysusG

   More actions

   Hi,

   This might be a stupid question, but I have tried the both methods to use a local stub: putting the pyi file in the same directory as the py file to run and exporting MYPMPATH to a stub directory and put the pyi file there. I named both pyi file the same name as the py file except for the extension. However, both situations does not throw an error when I run a test program with the incorrect typing hint.

   Is there some new way to use the new local stub or I was just stupid and misunderstand the instruction?
10. gvanrossum commented on May 31, 2016

    

    gvanrossum

    on May 31, 2016 via email

    Member

    More actions

    Can you provide more specific? Show exactly which files are where, what MYPYPATH is set to, and the error you are getting.

    …

    --Guido (mobile)
11. Kamforka commented on Jul 12, 2019

    

    Kamforka

    on Jul 12, 2019

    More actions

    So as a follow up I also can't seem to sort out the problems with local stub files.

    I have the following project structure:

    stub-typing/
    ├── stubtyping/
    │   ├── __init__.py
    │   ├── main.py
    │   └── main.pyi
    └── venv/
    

    main.py has the following content:

    def add(a, b):
        return a + b
    
    
    add(1, 2)
    add('a', 'b')

    and main.pyi has:

    def add(a: int, b: int) -> int: ...

    When MYPYPATH is unset and I execute mypy stubtyping/ I have a blank output instead of the expected:

    main.py:6: error: Argument 1 to "add" has incompatible type "str"; expected "int"
    main.py:6: error: Argument 2 to "add" has incompatible type "str"; expected "int"
    

    I also tried to setMYPYPATH to stubtyping/ but I still get the same results.

    What am I missing?
12. gvanrossum commented on Jul 12, 2019

    

    gvanrossum

    on Jul 12, 2019

    Member

    More actions

    Next time please use the Gitter channel (see project README).

    The answer is that mypy ignores main.py because it finds main.pyi in the same directory. This is by design. If you want type annotations, put then in main.py and get rid of main.pyi.