Skip to content

Check __setattr__ when property is not settable #9196

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

Merged
merged 5 commits into from
Sep 23, 2020
Merged

Check __setattr__ when property is not settable #9196

merged 5 commits into from
Sep 23, 2020

Conversation

kamilturek
Copy link
Contributor

Fixes #9160

Copy link
Collaborator

@JukkaL JukkaL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! This is almost ready for merging, but there are a some additional cases that would be nice to test/support.

@kamilturek kamilturek requested a review from JukkaL August 14, 2020 19:27
@rhshadrach
Copy link

@JukkaL friendly ping

Copy link
Collaborator

@hauntsaninja hauntsaninja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, and it looks like Jukka's concerns have been addressed. Thanks @kamilturek for your series of PRs! :-)

@hauntsaninja hauntsaninja merged commit 3186281 into python:master Sep 23, 2020
hauntsaninja pushed a commit to hauntsaninja/mypy that referenced this pull request Sep 23, 2020
@hauntsaninja
Copy link
Collaborator

Actually, I think I'm going to revert this, see #9474

hauntsaninja added a commit that referenced this pull request Sep 23, 2020
This reverts commit 3186281.

Co-authored-by: hauntsaninja <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

class with __setattr__ reports properties are read-only
5 participants