Skip to content

Fix mypyc breakage caused by mypy multiple inheritance bug - #6480

Merged
msullivan merged 1 commit into
masterfrom
fix-mypyc
Feb 25, 2019
Merged

msullivan merged 1 commit into
masterfrom
fix-mypyc

Conversation

@msullivan

Copy link
Copy Markdown
Collaborator

Bug #3603 strikes again. We've got this workaround in another place or
two.

I have a plan for a less bad workaround involving introducing a SymbolNodeFuncDef
class, but let's stop the bleeding first.

Bug #3603 strikes again. We've got this workaround in another place or
two.
@msullivan
msullivan merged commit 72a6b1b into master Feb 25, 2019
@msullivan
msullivan deleted the fix-mypyc branch February 25, 2019 21:55
msullivan added a commit that referenced this pull request Feb 25, 2019
…sues

A mypy bug (#3603) causes mypy to think that SymbolNodes cannot be
FuncBases, which causes mypy-mypyc to crash in code that tests
that.
Currently we work around this in a couple gross ways (like turning the
SymbolNode into Any). Work around it instead by testing directly
against a tuple of the subtypes instead of FuncBase itself.

This is the better fix promised in #6480.
msullivan added a commit that referenced this pull request Feb 28, 2019
#6481)

A mypy bug (#3603) causes mypy to think that SymbolNodes cannot be
FuncBases, which causes mypy-mypyc to crash in code that tests
that.
Currently we work around this in a couple gross ways (like turning the
SymbolNode into Any). Work around it instead by testing directly
against a tuple of the subtypes instead of FuncBase itself.

This is the better fix promised in #6480.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants