Skip to content

Optional strict checking of isinstance checks #4332

Closed

Description

@JukkaL

The current semantics of isinstance checks make some assumptions about inheritance, such as there being no multiple inheritance from certain classes. This is probably reasonable as a default, since it makes easier to annotate legacy codebases. However, we could provide an option to have safer and stricter checking of isinstance checks. The exact behavior of this mode is still not quite clear.

See discussion in #3605 for further context.

Activity

  1. ilevkivskyi commented on Dec 6, 2017

    @ilevkivskyi
    Member

    Just for the reference here is the previous proposal #3603 (comment)

  2. msullivan commented on Jan 28, 2020

    @msullivan
    Collaborator

    I don't think this meets the bar of adding a new flag and we're moving towards more intersection stuff

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions