-
Notifications
You must be signed in to change notification settings - Fork 30
Clear dict py314 #221
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
Clear dict py314 #221
Conversation
|
I ran the latest zope.meta configuration so that the addition of Python 3.14 is reflected everywhere instead of just the GHA version specification. I have no idea why the pypy-3.10 test on Windows is failing while looking for setuptools 78.1.1, that makes no sense. |
|
After reverting the setuptools version change the tests are turning green again. So there's yet another setuptools issue. What confuses me about the PyPy build (as a non-expert) is that the C extensions are built and that the build instructions in the |
dataflake
left a comment
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.
The setuptools issue is a separate problem, the dictionary fix should go ahead. I can't judge if that dictionary clearing has unwanted side effects, though.
|
Before this change, you can assign |
This is how the pure-Python implementation already works, so I believe that should be the expected behaviour: persistent/src/persistent/persistence.py Lines 453 to 458 in a5bafe1
Relstorage has tests that fail without this change, and which pass with this change and pass in +1 from me, and for getting this merged and released. |
Waiting for zopefoundation/persistent#221 to be released.
|
Just released in https://pypi.org/project/persistent/6.2/. |
Fix: #218
IMHO in python 3.14 dictionary and/or garbage optimization requires to explicitly clear the dictionary.
Although this change seems to fix the tests in python 3.14 (tested with python 3.14.0b2), I suggest double-checking the change with someone more familiar with the internals of the library to exclude any side effects related to the change