INTERNAL ERROR report

[mjpost]

Hi,

I get the following error when I run

mypy --ignore-missing-imports --follow-imports=silent @typechecked-files --no-strict-optional --show-traceback

from the root of Sockeye. I am not sure how to fix it or what causes it. Can you help?

./contrib/sacrebleu/sacrebleu.py: error: INTERNAL ERROR -- please report a bug at https://github.com/python/mypy/issues version: 0.610
Traceback (most recent call last):
  File "/usr/local/bin/mypy", line 11, in <module>
    sys.exit(console_entry())
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/__main__.py", line 7, in console_entry
    main(None)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/main.py", line 91, in main
    res = type_check_only(sources, bin_dir, options, flush_errors, fscache)  # noqa
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/main.py", line 148, in type_check_only
    fscache=fscache)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 185, in build
    flush_errors, fscache)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 285, in _build
    graph = dispatch(sources, manager)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 2398, in dispatch
    process_graph(graph, manager)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 2691, in process_graph
    process_stale_scc(graph, scc, manager)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 2801, in process_stale_scc
    graph[id].semantic_analysis()
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 2009, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath, self.options, patches)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 1818, in wrap_context
    yield
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/build.py", line 2009, in semantic_analysis
    self.manager.semantic_analyzer.visit_file(self.tree, self.xpath, self.options, patches)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 291, in visit_file
    v.type = self.anal_type(v.type)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 1578, in anal_type
    typ = t.accept(a)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/types.py", line 203, in accept
    return visitor.visit_unbound_type(self)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/typeanal.py", line 178, in visit_unbound_type
    typ = self.visit_unbound_type_nonoptional(t)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/typeanal.py", line 186, in visit_unbound_type_nonoptional
    sym = self.lookup(t.name, t, suppress_errors=self.third_pass)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 3058, in lookup_qualified
    n = self.lookup(parts[0], ctx, suppress_errors=suppress_errors)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 3038, in lookup
    self.name_not_defined(name, ctx)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 3246, in name_not_defined
    self.fail(message, ctx)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/semanal.py", line 3281, in fail
    self.errors.report(ctx.get_line(), ctx.get_column(), msg, blocker=blocker)
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/errors.py", line 260, in report
    target=self.current_target())
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/errors.py", line 208, in current_target
    return self.scope.current_target()
  File "/usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/mypy/scope.py", line 30, in current_target
    assert self.module
AssertionError: 
./contrib/sacrebleu/sacrebleu.py: : note: use --pdb to drop into pdb

[emmatyping]

This usually happens when the mypy install is broken or site-packages is in the path. How did you install mypy? Can you look for /usr/local/Cellar/python3/3.6.4/Frameworks/Python.framework/Versions/3.6/lib/mypy? If it doesn't exist, your install is broken. Otherwise, you might try install mypy from git, I've added some better debugging about how site-packages got into the PATH.

[mjpost]

Thanks — I installed through pip3, and no amount of uninstall/install would resolve the problem, but it installed fine through git as you suggested.

[gvanrossum]

I'd like to reopen this, because we've seen this internally too -- a user has installed Python 3 via brew (/Cellar/ in the path is the giveaway here), installed mypy using pip3, and then somehow mypy can't find typeshed resulting in this crash. It doesn't happen to everyone who uses brew though, and IIRC there's a way to fix it that doesn't require installing from git master (something with brew update and/or upgrading Python 3 perhaps).

[mjpost]

Sounds good. I’m happy to run anything if it would be helpful. I will note that after pip3 install mypy there was indeed no mypy file at the path noted by @ethanhs above.

[emmatyping]

If you could uninstall the git version and re-install normally, is there any folder named typeshed on your computer?

Also, I am going to up the priority of #5307, since we keep running into issues with data_files.

[mjpost]

Sorry to ask, but how do I uninstall from the git repo? Googling didn't turn up much. Is

rm $(which mypy)
rm -rf /usr/local/lib/python3.6/site-packages/*mypy*

sufficient? If so, after doing that, reinstalling mypy (pip3 install mypy), mypy still fails, and there is no typeshed folder, at least not where I looked:

find /usr/local/lib/python3.6/site-packages -name typshed
# → returns nothing

[emmatyping]

You can uninstall via pip uninstall mypy for future reference (sorry I probably should have mentioned that).

The typeshed folder is usually located outside of the site-packages, so it might be more useful to do find /usr/local -name typeshed. Hopefully this isn't horribly slow, if it is, you might try narrowing it to /usr/local/Cellar, which should help. Thank you for working with me on debugging this!

[mjpost]

Ok, I didn't realize I could uninstall with pip after installing with git. Though it makes sense.

I ran the following:

pip3 uninstall mypy
find /usr/local -name typeshed # → nothing
pip3 install mypy
find /usr/local -name typeshed # → /usr/local/lib/mypy/typeshed

But now the original error is back.

[emmatyping]

Aha! That confirms my theory. It looks like data files are installed in a different root than the mypy package (/usr/local/lib/ rather than /usr/local/Cellar/). Thanks so much for debugging this!

For now, I'd suggest using mypy from git again if you can, but hopefully we can figure out a fix before the next release (which is soon).

[mjpost]

Cool, glad I could help! I'm happy to use the workaround. Thanks for helping me out.