-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
Doc on weakref.proxy should mention ReferenceError #98348
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
Labels
docs
Documentation in the Doc dir
Comments
@fancidev are you willing to send a PR? :) |
Here you go! |
JelleZijlstra
pushed a commit
that referenced
this issue
Oct 26, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Oct 26, 2022
…pythonGH-98355) (cherry picked from commit 216f45e) Co-authored-by: fancidev <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Oct 26, 2022
…pythonGH-98355) (cherry picked from commit 216f45e) Co-authored-by: fancidev <[email protected]>
miss-islington
added a commit
that referenced
this issue
Oct 26, 2022
…8355) (cherry picked from commit 216f45e) Co-authored-by: fancidev <[email protected]>
miss-islington
added a commit
that referenced
this issue
Oct 26, 2022
…8355) (cherry picked from commit 216f45e) Co-authored-by: fancidev <[email protected]>
Thanks, looks like this was completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The documentation on weakref.proxy does not say what happens if an attribute of the proxy object is accessed when the referent is gone. I had to do a bit of googling to find out it raises ReferenceError.
Would be helpful to mention that in the doc of weakref.proxy.
The text was updated successfully, but these errors were encountered: