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.

Sign up for GitHub

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

Jump to bottom

Clarify the implications of subclassing Any #1747

Closed

carljm opened this issue May 23, 2024 · 1 comment

Labels

topic: typing spec

Member

carljm commented May 23, 2024 •

edited

Loading

The typing spec says

Any can also be used as a base class. This can be useful for avoiding type checker errors with classes that can duck type anywhere or are highly dynamic.

But this leaves some cases unclear. The unclear cases are described in https://discuss.python.org/t/take-2-rules-for-subclassing-any/47981

One possible solution was explored in #1672, but rejected due to issues uncovered in https://discuss.python.org/t/take-2-rules-for-subclassing-any/47981/19

JelleZijlstra added the topic: typing spec label

Member

JelleZijlstra commented May 23, 2024

Duplicate of #1546

JelleZijlstra marked this as a duplicate of #1546

JelleZijlstra closed this as not planned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment