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

when inheriting from tuple, incomplete-protocol false positive #25

Closed
pylint-bot opened this issue Jun 13, 2013 · 3 comments
Closed

when inheriting from tuple, incomplete-protocol false positive #25

pylint-bot opened this issue Jun 13, 2013 · 3 comments
Labels
Bug 🪲 Checkers Related to a checker

Comments

@pylint-bot
Copy link

Originally reported by: Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?)


complains about missing delitem, setitem which don't make sense on (immutable) tuple


@pylint-bot
Copy link
Author

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):


[design analysis] fix badly implemented protocol for read-only containers like tuple. Close #25

@pylint-bot
Copy link
Author

Original comment by Yanir Seroussi (BitBucket: yanir, GitHub: @yanir?):


We're seeing a similar issue with a container that inherits from set ("Badly implemented Container, implements len but not getitem"). Is may be worth adding checks for containers that inherit from containers that don't support random access.

@pylint-bot
Copy link
Author

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):


Removing version: 1.0 (automated comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🪲 Checkers Related to a checker
Projects
None yet
Development

No branches or pull requests

1 participant