You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the Python documentation isn't too explicit about what this function was used for (no examples)
the subtle difference between tp_getattr/tp_settatr and tp_getattro/tp_setattro could be clearer (beside the fact that the first ones are outdated).
there are two cases: you can use the PyObject_GenericG/SetAttr or not, but the criteria for this decision are unclear to me.
If you can use the Generic functions, you don't need Py_FindMethod so that's easy, but there are no explanations if you can't (which seems to be my specific case) on how to get rid of the method without breaking your code.
So quite a lot of missing explanations, I think, which you could possibly highlight in an update.
The text was updated successfully, but these errors were encountered:
There are indeed many obscure differences, especially in C-extensions, and there exists no exhaustive list of what those differences are, so I have made no attempt of trying to cover all changes when it comes to the C API.
A list of common changes would be good, but honestly, for everything that isn't covered, I've only ever gotten one email issue per API call that changed, and only something like 3 or 4 issues/emails about the C API in total.
I'll keep the issue open, and Google searches should find it if anyone else uses this method.
Your book, especially http://python3porting.com/cextensions.html, has already been very helpful to start porting rdiff-backup to Python3, but I'm stuck on the disappearance of Py_FindMethod as used in rdiff_backup/_librsyncmodule.c. According to my research:
So quite a lot of missing explanations, I think, which you could possibly highlight in an update.
The text was updated successfully, but these errors were encountered: