Fail fast if special module like typing not from typeshed #1876

drakedevel · 2016-07-15T20:05:57Z

mypy generally crashes with an internal error if it winds up trying to handle a file named typing.py, apparently due to confusion with the built-in typing module. Here's the simplest test case I've found (tested on 0.4.3 and master):

(mypyve) vm:/tmp/test1$ cat typing.py 
from collections import namedtuple

x = namedtuple('x', [])
(mypyve) vm:/tmp/test1$ mypy -s typing.py 
Traceback (most recent call last):
  File "/tmp/mypyve/bin/mypy", line 6, in <module>
    main(__file__)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 40, in main
    res = type_check_only(sources, bin_dir, options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 81, in type_check_only
    options=options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 177, in build
    dispatch(sources, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1338, in dispatch
    process_graph(graph, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1481, in process_graph
    process_stale_scc(graph, scc)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1554, in process_stale_scc
    graph[id].semantic_analysis()
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1303, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 243, in visit_file
    self.accept(d)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 2307, in accept
    node.accept(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/nodes.py", line 761, in accept
    return visitor.visit_assignment_stmt(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1076, in visit_assignment_stmt
    self.process_namedtuple_definition(s)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1416, in process_namedtuple_definition
    named_tuple = self.check_namedtuple(s.rvalue, name)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1454, in check_namedtuple
    info = self.build_namedtuple_typeinfo(name, items, types)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1543, in build_namedtuple_typeinfo
    info.mro = [info] + info.tuple_type.fallback.type.mro
TypeError: can only concatenate list (not "NoneType") to list

*** INTERNAL ERROR ***

typing.py:3: error: Internal error -- please report a bug at https:/python/mypy/issues

NOTE: you can use "mypy --pdb ..." to drop into the debugger when this happens.

This is the same error message reported in a comment in #1293. The root cause is that mypy ships a file called typing.py in site-packages, so if site-packages winds up on the path (even implicitly, even with -s), it dies:

(mypyve) vm:/tmp/mypyve/lib/python3.4/site-packages$ mypy -s typing.py 
Traceback (most recent call last):
...
(mypyve) vm:/tmp/mypyve/lib/python3.4/site-packages$ touch hello.py
(mypyve) vm:/tmp/mypyve/lib/python3.4/site-packages$ mypy -s hello.py 
Traceback (most recent call last):
...

This makes it impossible to analyze a package along with even a subset of its dependencies as the implicit addition to MYPYPATH results in an internal error.

The text was updated successfully, but these errors were encountered:

gvanrossum · 2016-07-15T20:52:09Z

We apologize for the crash and will look into producing a more meaningful error message.

Is the file typing.py that you have a copy of the official typing.py file or an unrelated file with an unfortunate name clash?

When analyzing a package and its dependencies it's usually best not to include site-packages -- there's an explicit warning about this in the docs (see the very bottom of http://mypy.readthedocs.io/en/latest/basics.html).

drakedevel · 2016-07-15T21:33:39Z

The first example simulates the "unfortunate name clash" case, contents of the file displayed. The second example it is the official typing.py taken from git master shortly before I posted this issue.

Note that in neither case did I explicitly set MYPYPATH. Just referencing a file in the site-packages directory (which implicitly adds it to the search path) is sufficient.

I ran into this while setting up mypy for the first time after having added the venv site-packages to the MYPYPATH variable in response to the tremendous number of import errors from the first run for libraries that I knew were installed. I only read mypy --help so I didn't see the warning in the docs until significantly later.

I thought it would be reasonable to "whitelist" site-packages that were known to be analyzable, with an invocation like mypy -s src/ venv/.../site-packages/tiny_lib/. If library authors add types going forward, this seems like a preferable approach to out-of-tree stubs. Unfortunately, today this adds the whole of site-packages to the path implicitly, and then this bug causes an internal error.

gvanrossum · 2016-07-15T21:39:50Z

Yeah, the feature of automatically adding the parent directory to the import path fails spectacularly for site-packages -- perhaps we should just exclude site-packages from this behavior even if we preserve it for other locations (because it is often truly useful as well!).

We've also discussed the idea of a flag that adds a stdlib module to the packages to be analyzed (without this auto-path-setting behavior).

When you have a tremendous number of failing imports, you may also consider --silent-imports -- see here for the docs: http://mypy.readthedocs.io/en/latest/command_line.html#following-imports-or-not

drakedevel · 2016-07-15T21:47:02Z

Yeah, I started using -s after I found that page. Our codebase has a lot of dependencies, including sqlalchemy and a few other heavyweights so it looks like there's no other options for now. I was a little surprised to discover that even with -s, even if I specify only a single file to analyze, it will process other files in the path (like typing.py!) It makes sense but the semantics could be more clearly documented.

gvanrossum · 2016-07-15T22:09:03Z

Actually typing.py is probably the exception. What does -v output for a single file? There's a little cycle of dependencies around builtins (at least builtins, typing, and abc) but typically these are gotten from typeshed stubs, not from .py files.

drakedevel · 2016-07-15T22:13:53Z

Is this what you wanted?

(mypyve) vm:/tmp/test5$ cat typing.py 
from collections import namedtuple
x = namedtuple('x', [])
(mypyve) vm:/tmp/test5$ mypy -vs typing.py 
0.000:LOG:  Using new dependency manager
0.000:LOG:  Parsing typing.py (typing)
0.001:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/collections/__init__.pyi (collections)
0.010:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/builtins.pyi (builtins)
0.089:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/abc.pyi (abc)
0.090:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/sys.pyi (sys)
0.098:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/types.pyi (types)
0.109:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/_importlib_modulespec.pyi (_importlib_modulespec)
0.112:LOG:  Loaded graph with 7 nodes
0.113:LOG:  Found 1 SCCs; largest has 7 nodes
0.113:LOG:  Processing SCC of size 7 (abc collections typing _importlib_modulespec types sys builtins) as inherently stale (_importlib_modulespec abc builtins collections sys types typing)
Traceback (most recent call last):
  File "/tmp/mypyve/bin/mypy", line 6, in <module>
    main(__file__)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 40, in main
    res = type_check_only(sources, bin_dir, options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 81, in type_check_only
    options=options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 177, in build
    dispatch(sources, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1338, in dispatch
    process_graph(graph, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1481, in process_graph
    process_stale_scc(graph, scc)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1554, in process_stale_scc
    graph[id].semantic_analysis()
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1303, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 243, in visit_file
    self.accept(d)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 2307, in accept
    node.accept(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/nodes.py", line 761, in accept
    return visitor.visit_assignment_stmt(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1076, in visit_assignment_stmt
    self.process_namedtuple_definition(s)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1416, in process_namedtuple_definition
    named_tuple = self.check_namedtuple(s.rvalue, name)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1454, in check_namedtuple
    info = self.build_namedtuple_typeinfo(name, items, types)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1543, in build_namedtuple_typeinfo
    info.mro = [info] + info.tuple_type.fallback.type.mro
TypeError: can only concatenate list (not "NoneType") to list

*** INTERNAL ERROR ***

typing.py:2: error: Internal error -- please report a bug at https:/python/mypy/issues

NOTE: you can use "mypy --pdb ..." to drop into the debugger when this happens.
0.119:LOG:  Build finished with 7 modules, 0 types, and 57 errors

gvanrossum · 2016-07-15T22:24:36Z

That one's not so surprising because you pass a bogus typing.py on the command line -- this gets substituted for the stub in typeshed so that whatever builtins needs from typing isn't there, and hence the crash. I thought that you were reporting problems when passing foo.py on the command line where there's a bogus typing.py in the same directory when also passing -s. Also, what version of mypy? I can repro this with 0.4.3-dev but not with 0.4.3.

drakedevel · 2016-07-15T22:34:39Z

Here's the case with that same typing.py alongside an empty hello.py with 0.4.3:

(app) vm:/tmp/test5$ cat typing.py 
from collections import namedtuple
x = namedtuple('x', [])
(app) vm:/tmp/test5$ cat hello.py 
(app) vm:/tmp/test5$ mypy --version
mypy 0.4.3
(app) vm:/tmp/test5$ mypy -sv hello.py 
0.000:LOG:  Using new dependency manager
0.000:LOG:  Parsing hello.py (hello)
0.001:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/builtins.pyi (builtins)
0.077:LOG:  Parsing /tmp/test5/typing.py (typing)
0.078:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/abc.pyi (abc)
0.079:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/collections/__init__.pyi (collections)
0.087:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/sys.pyi (sys)
0.096:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/types.pyi (types)
0.106:LOG:  Parsing /home/adrake/ve/app/lib/mypy/typeshed/stdlib/3/_importlib_modulespec.pyi (_importlib_modulespec)
0.109:LOG:  Loaded graph with 8 nodes
0.109:LOG:  Found 2 SCCs; largest has 7 nodes
0.110:LOG:  Processing SCC of size 7 (collections abc typing _importlib_modulespec types sys builtins) as inherently stale (_importlib_modulespec abc builtins collections sys types typing)
Traceback (most recent call last):
  File "/home/adrake/ve/app/bin/mypy", line 6, in <module>
    main(__file__)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/main.py", line 40, in main
    res = type_check_only(sources, bin_dir, options)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/main.py", line 81, in type_check_only
    options=options)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/build.py", line 177, in build
    dispatch(sources, manager)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/build.py", line 1323, in dispatch
    process_graph(graph, manager)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/build.py", line 1461, in process_graph
    process_stale_scc(graph, scc)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/build.py", line 1534, in process_stale_scc
    graph[id].semantic_analysis()
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/build.py", line 1288, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 243, in visit_file
    self.accept(d)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 2306, in accept
    node.accept(self)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/nodes.py", line 761, in accept
    return visitor.visit_assignment_stmt(self)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 1075, in visit_assignment_stmt
    self.process_namedtuple_definition(s)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 1415, in process_namedtuple_definition
    named_tuple = self.check_namedtuple(s.rvalue, name)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 1453, in check_namedtuple
    info = self.build_namedtuple_typeinfo(name, items, types)
  File "/home/adrake/ve/app/lib/python3.4/site-packages/mypy/semanal.py", line 1542, in build_namedtuple_typeinfo
    info.mro = [info] + info.tuple_type.fallback.type.mro
TypeError: can only concatenate list (not "NoneType") to list

*** INTERNAL ERROR ***

/tmp/test5/typing.py:2: error: Internal error -- please report a bug at https:/python/mypy/issues

NOTE: you can use "mypy --pdb ..." to drop into the debugger when this happens.
0.116:LOG:  Build finished with 8 modules, 0 types, and 57 errors
(app) vm:/tmp/test5$

And here's git master, same file setup:

(mypyve) vm:/tmp/test5$ mypy --version
mypy 0.4.4-dev
(mypyve) vm:/tmp/test5$ mypy -sv hello.py 
0.000:LOG:  Using new dependency manager
0.000:LOG:  Parsing hello.py (hello)
0.001:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/builtins.pyi (builtins)
0.079:LOG:  Parsing /tmp/test5/typing.py (typing)
0.080:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/abc.pyi (abc)
0.081:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/collections/__init__.pyi (collections)
0.089:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/sys.pyi (sys)
0.096:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/types.pyi (types)
0.107:LOG:  Parsing /tmp/mypyve/lib/mypy/typeshed/stdlib/3/_importlib_modulespec.pyi (_importlib_modulespec)
0.110:LOG:  Loaded graph with 8 nodes
0.110:LOG:  Found 2 SCCs; largest has 7 nodes
0.110:LOG:  Processing SCC of size 7 (collections abc typing _importlib_modulespec types sys builtins) as inherently stale (_importlib_modulespec abc builtins collections sys types typing)
Traceback (most recent call last):
  File "/tmp/mypyve/bin/mypy", line 6, in <module>
    main(__file__)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 40, in main
    res = type_check_only(sources, bin_dir, options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/main.py", line 81, in type_check_only
    options=options)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 177, in build
    dispatch(sources, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1338, in dispatch
    process_graph(graph, manager)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1481, in process_graph
    process_stale_scc(graph, scc)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1554, in process_stale_scc
    graph[id].semantic_analysis()
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/build.py", line 1303, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 243, in visit_file
    self.accept(d)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 2307, in accept
    node.accept(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/nodes.py", line 761, in accept
    return visitor.visit_assignment_stmt(self)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1076, in visit_assignment_stmt
    self.process_namedtuple_definition(s)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1416, in process_namedtuple_definition
    named_tuple = self.check_namedtuple(s.rvalue, name)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1454, in check_namedtuple
    info = self.build_namedtuple_typeinfo(name, items, types)
  File "/tmp/mypyve/lib/python3.4/site-packages/mypy/semanal.py", line 1543, in build_namedtuple_typeinfo
    info.mro = [info] + info.tuple_type.fallback.type.mro
TypeError: can only concatenate list (not "NoneType") to list

*** INTERNAL ERROR ***

/tmp/test5/typing.py:2: error: Internal error -- please report a bug at https:/python/mypy/issues

NOTE: you can use "mypy --pdb ..." to drop into the debugger when this happens.
0.116:LOG:  Build finished with 8 modules, 0 types, and 57 errors

gvanrossum · 2016-07-15T23:01:55Z

Hm, the only reasonable way that I can think to avoid such crashes is to explicitly check that the stub for typing, builtins and everything else in that initial import cycle is actually loaded from typeshed. Hopefully you can work around it now!

drakedevel · 2016-07-15T23:07:41Z

Was there a workaround for wanting to include a venv dependency in the analysis? Or is that future work

gvanrossum · 2016-07-15T23:26:47Z

That's future work -- a cumbersome workaround would be to just download and untar the tarball (or unzip the zipfile) for the package's source distro, or clone the repo, and point mypy at the package in the source tree. For most reasonable source distributions that should work.

gvanrossum · 2016-07-27T05:07:05Z

See PR #1895 -- once that lands anybody can install typeshed additions.

gvanrossum · 2016-11-01T15:41:20Z

I don't think finding a solution that avoids the initially-reported crash has much priority. When you feed mypy the wrong typing.py (or builtins.py, or whatever) it's going to be unhappy. So I'm moving the milestone up.

gvanrossum · 2016-11-01T22:47:02Z

Random idea: I wonder if we should have a separate panic() function for reporting problems like this (notably things missing from the builtins), so that they are clearly distinguished from other crashes?

gvanrossum · 2016-12-09T20:17:11Z

I propose to close this as "won't fix" since we're unlikely to be fixing crashes due to the presence of incorrect stubs for builtins and typing.

JukkaL · 2016-12-09T21:03:59Z

What about checking that typing and builtins come from typeshed?

gvanrossum · 2016-12-09T21:50:41Z

Sure. (And their dependencies, I suppose -- I have "_importlib_modulespec,abc,types,builtins,typing,sys" listed for PY3.

If you want that in this same issue please rename the issue subject.

JukkaL · 2016-12-09T23:11:47Z

Ok, renamed. Let's continue to use this issue.

msullivan · 2021-02-19T23:41:35Z

This has regressed again. If you do something like mypy -m typing, it works correctly (which is why the test still passes), but if you do mypy typing.py or mypy some_dir_with_typing, it will break, because it gets loaded directly without going through find_module_and_diagnose.

(Additionally something changed between 0.790 and 0.812 that caused mypy to start picking up edb/tools/flake8/typing.py (with flake8 not having a __init__) as typing. This is probably a bug fix, since is seems like that's what should happen, but since it causes a crash it was kind of painful.)

hauntsaninja · 2021-02-19T23:50:58Z

v0.800 made a number of changes to source finding behaviour, in particular recursively finding code that we used to not find. v0.812 has a new flag --exclude which you can use to ignore the badness causing file (https://mypy.readthedocs.io/en/stable/command_line.html#cmdoption-mypy-exclude)

JukkaL · 2021-02-21T17:43:23Z

Even though --exclude can be used as a workaround, we shouldn't crash if there's a module named typing. So I agree that this is a regression. Not sure if this is important enough to make a point release. Thoughts?

shrutidst · 2021-03-13T03:30:13Z

@JukkaL this issue seems to be open. Can you assign it to me?

hauntsaninja · 2021-03-13T05:30:35Z

Feel free to work on it. No one really takes issue assignment in mypy to mean anything

It should work now with custom-typeshed-dir and use_builtins_fixtures. Fixes python#1876

It should work now with custom-typeshed-dir. Fixes python#1876

It should work now with custom-typeshed-dir. Fixes #1876

gvanrossum added the crash label Jul 15, 2016

gvanrossum added this to the 0.4.x milestone Jul 15, 2016

gvanrossum modified the milestones: 0.5, 0.4.x Nov 1, 2016

JukkaL changed the title ~~Several issues with files named typing.py~~ Fail fast if special module like typing not from typeshed Dec 9, 2016

gvanrossum added the priority-1-normal label Jan 6, 2017

gvanrossum removed this from the 0.5 milestone Mar 29, 2017

ilevkivskyi added the topic-usability label May 19, 2017

ilevkivskyi mentioned this issue Jul 31, 2017

Crash on simple namedtuple #3781

Closed

ethanhs mentioned this issue Sep 6, 2017

working with third party libs without stubs #3930

Closed

ilevkivskyi mentioned this issue Dec 1, 2017

Crash when passing non-existant directory as --custom-typeshed-dir #4301

Closed

JukkaL added the priority-0-high label Dec 1, 2017

hauntsaninja mentioned this issue Jun 26, 2021

Mypy v0.910 crash in stdlib typeshed with file named typing.py under a websockets directory #10722

Closed

NeilGirdhar mentioned this issue Feb 16, 2022

Remove float32 dtype assumption google/flax#1803

Closed

3 tasks

ethanhs mentioned this issue Jun 7, 2022

[WIP] Fail fast if module like typing not from typeshed #12955

Closed

JukkaL removed their assignment Jun 15, 2022

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 16, 2022

Ensure builtin modules are from typeshed sooner

8d8350a

It should work now with custom-typeshed-dir and use_builtins_fixtures. Fixes python#1876

code-of-kpp mentioned this issue Jul 16, 2022

Ensure builtin modules are from typeshed sooner #13155

Merged

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 16, 2022

Ensure builtin modules are from typeshed sooner

9d42785

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 16, 2022

Ensure builtin modules are from typeshed sooner

d40f6d4

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

0ba3d21

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

d7227b3

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

3d2f8a2

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

15617d1

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

0dfa86e

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

61f92e6

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

087db77

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

06a9b22

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

4980baa

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

f520c57

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

fc20f99

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

b231fd9

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

1549fa8

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 17, 2022

Ensure builtin modules are from typeshed sooner

2fcb933

It should work now with custom-typeshed-dir. Fixes python#1876

code-of-kpp pushed a commit to code-of-kpp/mypy that referenced this issue Jul 30, 2022

Ensure builtin modules are from typeshed sooner

f1a2722

It should work now with custom-typeshed-dir. Fixes python#1876

ilevkivskyi closed this as completed in #13155 Jul 31, 2022

ilevkivskyi pushed a commit that referenced this issue Jul 31, 2022

Ensure builtin modules are from typeshed sooner (#13155)

cbabbf7

It should work now with custom-typeshed-dir. Fixes #1876

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fail fast if special module like typing not from typeshed #1876

Fail fast if special module like typing not from typeshed #1876

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

gvanrossum commented Jul 27, 2016

gvanrossum commented Nov 1, 2016

gvanrossum commented Nov 1, 2016

gvanrossum commented Dec 9, 2016

JukkaL commented Dec 9, 2016

gvanrossum commented Dec 9, 2016

JukkaL commented Dec 9, 2016

msullivan commented Feb 19, 2021

hauntsaninja commented Feb 19, 2021 •

edited

Loading

JukkaL commented Feb 21, 2021

shrutidst commented Mar 13, 2021

hauntsaninja commented Mar 13, 2021

Fail fast if special module like typing not from typeshed #1876

Fail fast if special module like typing not from typeshed #1876

Comments

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

drakedevel commented Jul 15, 2016

gvanrossum commented Jul 15, 2016 via email

gvanrossum commented Jul 27, 2016

gvanrossum commented Nov 1, 2016

gvanrossum commented Nov 1, 2016

gvanrossum commented Dec 9, 2016

JukkaL commented Dec 9, 2016

gvanrossum commented Dec 9, 2016

JukkaL commented Dec 9, 2016

msullivan commented Feb 19, 2021

hauntsaninja commented Feb 19, 2021 • edited Loading

JukkaL commented Feb 21, 2021

shrutidst commented Mar 13, 2021

hauntsaninja commented Mar 13, 2021

hauntsaninja commented Feb 19, 2021 •

edited

Loading