-
Notifications
You must be signed in to change notification settings - Fork 970
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
Fix wrong is_namedtuple
implementation
#2475
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
pytest is bugged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the function.
It looks like the old code corresponds to this old SO answer whereas the new code corresponds to a more recent SO answer. It always pays to check more than the first SO answer :)
Since you provide code to check this, it could be added as a unit test, WDYT?
pytest is bugged
Yes, it's unrelated, should be fixed by #2461.
@BenjaminBossan added a test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix !
As per title.
The current implementation does not work in case of nested inheritance. Example:
giving
Using instead https://stackoverflow.com/questions/2166818/how-to-check-if-an-object-is-an-instance-of-a-namedtuple/62692640#62692640
cc @Giuseppe5 @nickfraser