-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Support "x = property(...)" in class body #8083
Labels
false-positive
mypy gave an error on correct code
feature
priority-1-normal
topic-descriptors
Properties, class vs. instance attributes
Comments
JukkaL
added
feature
priority-1-normal
false-positive
mypy gave an error on correct code
labels
Dec 5, 2019
I am not sure if this should be a separate issue.. I couldn't find the issue for properties outside of class body.. I am leaving this comment here, maybe it will help with testing of a future mypy implementation
I see that you can define properties outside of a class body.
|
Is there any known workaround for this? |
AlexWaygood
added
the
topic-descriptors
Properties, class vs. instance attributes
label
Aug 25, 2023
chrysn
added a commit
to chrysn/aiocoap
that referenced
this issue
May 12, 2024
This includes one actual bugfix found by mypy: Group setups where one algorithm was None (eg. no signing mode supported) would have raised an exception trying to access `None.value`. Includes-Workaround-For: python/mypy#8083
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
false-positive
mypy gave an error on correct code
feature
priority-1-normal
topic-descriptors
Properties, class vs. instance attributes
Currently it's not possible to define a property using
x = property(...)
in the class body.(Originally from #220.)
The text was updated successfully, but these errors were encountered: