-
Notifications
You must be signed in to change notification settings - Fork 68
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
ValueError
in a finalizer on PyPy
#98
Comments
This is not a remnant, but a way to cleanly fail instead of having the finalizer randomly break (ex: on interpreter shutdown). So if two finalizers fall into the same entry in Could you post more of the traceback which leads to this failure ? Especially, I wonder which class' Also, do you have a suggestion to clarify the intent of those raises, so they do not look like they may be leftover debugging code ? EDIT: finalization order happens because references to the required objects are held by the finalizer itself, not by |
That was |
Is there a way for me to try to replicate this issue ? I unfortunately have very little time these days (which I would otherwise spend trying to get the new python-libusb1 version out, master has several improvements which were long overdue) but maybe I can figure something out. At least, I did a quick try of the In case you would like to reproduce, it goes like this: Terminal 1, in
Terminal 2, in
But this may be too simple of an example to have a chance of triggering the issue. |
Unfortunately the way I discovered it is by running an userspace RGMII PHY driver with Glasgow on PyPy3.9. |
When running code that works fine on CPython under PyPy, I'm getting a
ValueError
raised here:Is this just a remnant on some debug code that happens to work by chance on CPython, or is there an actual reason to raise it? I'm very confused.
I'm using python-libusb1 3.1.0.
The text was updated successfully, but these errors were encountered: