Repository navigation
Error for metaclass conflict could be improved #6176
Description
When a metaclass conflict occurs, the current error message doesn't provide any details about which metaclasses are conflicting.
class Meta1(type): ...
class Base1(metaclass=Meta1): ...
class Meta2(type): ...
class Base2(metaclass=Meta2): ...
class Child(Base1, Base2): ... # Error: metaclass conflictIt would be helpful if pyright included the conflicting metaclasses to help in the diagnosis of the error.
Activity
Improved the error message for metaclass conflicts so the conflicting…
erictraut commentedon Oct 16, 2023
The message now includes the metaclasses:
erictraut commentedon Oct 18, 2023
This is included in pyright 1.1.332, which I just published. It will also be included in a future release of pylance.