Conversation
As a result of the checks made about the objectpointers in PyO3, all errors in PyWeakref_GetObject are already caught. Therefor there is no need to check for these errors in the non-ffi layer.
|
There are some issues with the new |
CodSpeed Performance ReportMerging #3835 will not alter performanceComparing Summary
|
d24fc7c to
dff0914
Compare
|
Thank you and sorry for the slow review, I will try my best to finally look at this tomorrow... |
No problem, completely understandable. I also ran into one last issue, PyPy does not include all the required bindings for the The type-objects for the reference types are not exported (not bound to in |
davidhewitt
left a comment
There was a problem hiding this comment.
Thank you very much for this!
It looked like a big diff but that's because you've included all docs and tests, thank you 🙏
I've given this a full read; I have a few initial things which need discussing and changing. I think once those are decided upon & done I might need to take another final read through just due to the size of the diff.
|
Regarding PyPy, for now I suggest just not offering these types on PyPy. |
|
It should be fixed now. I have looked into the Netlify error, it happens on |
|
Some tests are failing, I will change them to work with the new changes |
|
It should now work (I have now also tested on Python 3.13) |
|
Let's have another go 👍 |
|
I'm going to retry again - it seems to me like it's just cancelling jobs for no clear reason, which is odd. |
|
Ok, this time it failed with a hypothesis flake which I've not seen before. I've never experienced the CI so unreliable 😢 |
|
It's always I find it suspicious... |
|
Let's retry; other stuff is merging ok since. If this still struggles to merge then I think more investigation here of what on this branch is causing the issue. |
#3134 Add
PyWeakRef,PyWeakProxyandPyWeakCallableProxytypes, corresponding to Python'sweakref.ReferenceType,weakref.ProxyTypeandweakref.CallableProxyType.