Skip to content
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

Refurb crashes on Mypy 1.7.0 #16497

Open
dosisod opened this issue Nov 15, 2023 · 2 comments
Open

Refurb crashes on Mypy 1.7.0 #16497

dosisod opened this issue Nov 15, 2023 · 2 comments
Labels
bug mypy got something wrong question topic-mypyc mypyc bugs

Comments

@dosisod
Copy link
Contributor

dosisod commented Nov 15, 2023

Bug Report

Refurb is a project that depends on Mypy internals to work properly. Since v1.7.0 of Mypy (specifically since #15770 was merged), Refurb no longer works, and instead emits the following error:

$ refurb file.py
interpreted classes cannot inherit from compiled traits

See also: dosisod/refurb#305

To Reproduce

$ pip install refurb==1.22.2 mypy==1.7.0
$ touch file.py
$ refurb file.py
interpreted classes cannot inherit from compiled traits

Expected Behavior

Refurb doesn't crash.

Actual Behavior

Refurb is crashing.

Your Environment

  • Mypy version used: 1.7.0
  • Python version used: 3.11.5

Background

#15770 added a @trait decorator to TraverserVisitor, meaning 3rd party (interpreted) programs can no longer inherit from TraverserVisitor:

mypy/mypy/traverser.py

Lines 97 to 99 in c6cb3c6

@trait
@mypyc_attr(allow_interpreted_subclasses=True)
class TraverserVisitor(NodeVisitor[None]):

I tried a bunch of different workarounds including making a custom __new__ method, copy-and-pasting TraverserVisitor into my code and removing the @trait, but alas nothing is working, and so I had to pin Mypy to <= v1.6.1 in Refurb, which will prevent users from using the newest version of Mypy with Refurb. Using the non-compiled version of Mypy doesn't have this issue, but doing so would be far too slow, especially since Refurb parses/walks the full, fine-grained AST tree (similar to mypyd).

My question: How should I get around this? Is there anything I can do on my end, or does something in Mypy have to change? I would think that allow_interpreted_subclasses=True would nullify the inheritance restriction imposed by @trait, but that doesn't seem to be the case.

There is also the bigger question of how 3rd parties should safely use Mypy internals (or if they even should in the first place). Currently Mypy internals are not versioned and can change with any release. In addition, certain parts of Mypy are hard/impossible to use outside of Mypy itself, whether that's because they don't work, crash, or require lots of moving parts because they weren't meant to be used in a stand-alone environment. I know that standardizing/stabilizing Mypy's internals so that 3rd parties can use them is probably not a major priority, but I thought I would bring it up to gauge how you all feel about it. I could elaborate more but I want to keep this short. I can open a separate issue for this if need be.

@dosisod dosisod added the bug mypy got something wrong label Nov 15, 2023
@ilevkivskyi ilevkivskyi added the topic-mypyc mypyc bugs label Nov 15, 2023
@mr-c
Copy link
Contributor

mr-c commented Nov 16, 2023

This issue is also of interest to Debian, so a hack to fix this (here and/or in refurb) would be appreciated!

@ilevkivskyi
Copy link
Member

I would think that allow_interpreted_subclasses=True would nullify the inheritance restriction imposed by @trait, but that doesn't seem to be the case.

I definitely remember we wanted to allow this, but probably this is still not done. Anyway, an idea worth trying is to move @trait from TraverserVisitor to BaseStubGenerator. I guess there are more people who want to inherit from the former, while the latter is quite niche.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mypy got something wrong question topic-mypyc mypyc bugs
Projects
None yet
Development

No branches or pull requests

4 participants