gh-111138: Add PyList_Extend() and PyList_Clear() functions#111862
Conversation
|
This change keeps the internal C API: |
Sorry, something went wrong.
|
Oh, these functions should be added to the limited C API. |
Sorry, something went wrong.
|
@serhiy-storchaka @eendebakpt: I addressed your review. Please review updated PR. I also added a note about the corner case of finalizer modifying the list, and I even added tests on this corner case. |
Sorry, something went wrong.
|
I removed notes form the documentation about finalizers which can modify the list while PyList_Clear() and PyList_SetSlice(). |
Sorry, something went wrong.
|
I suggest to change exceptions to SystemError. It is easier to change from SystemError to other type if needed than in the other direction. |
Sorry, something went wrong.
Ok, done. |
Sorry, something went wrong.
Done: I added the functions to the limited C API version 3.13. |
Sorry, something went wrong.
|
@encukou: I added these 2 "new" functions to the limited C API. |
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I think there was a value in the note about possible non-emptiness of the list after clear(), but it can be added later, and perhaps in different form. The false assumption that the list is empty after clear() can lead to more severe bugs in C than in Python. It is not only about modifying the list in the item's destructor, it is mainly about releasing the GIL and modifying the list in other thread.
I left some suggestions for the documentation. I also think that it is better to move the documentation for new functions just past the documentation for PyList_SetSlice. The order here is not lexicographical, but semantical.
The rest LGTM.
Sorry, something went wrong.
The problem is that Python API is also affected. Other mutable and mapping types are affected. Should we add note in all Python and C functions which might be affected by the issue? I added the note since it exists in the C implementation. But I concur with Antoine, it's not worth it to confuse users about this corner case. |
Sorry, something went wrong.
I applied your suggestions.
Right, it's semantical. I moved PyList_Clear(), but left Extend after Append. For me, they go together :-) Maybe functions should just be sorted :-) |
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
You moved PyList_Clear() after PyList_SET_ITEM(), not after PyList_SetSlice().
The reason of moving PyList_Clear() and PyList_Extend() after PyList_SetSlice() is that functions that work with a single item go first, followed by functions that work with multiple items, and that both PyList_Clear() and PyList_Extend() are convenient functions for particular use cases of PyList_SetSlice().
Sorry, something went wrong.
|
Ok, I moved the functions after PyList_SetSlice() in the doc. |
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
Please wait until we have a better process for adding to the limited API -- e.g. until the WG is formed and can discuss this. |
Sorry, something went wrong.
I modified the PR just before you added this comment to not add these functions to the stable ABI / limited C API :-) |
Sorry, something went wrong.
* Split list_extend() into two sub-functions: list_extend_fast() and list_extend_iter(). * list_inplace_concat() no longer has to call Py_DECREF() on the list_extend() result, since list_extend() now returns an int.
32f6976 to
751158a
Compare
November 13, 2023 15:46
I also moved the definition to Include/cpython/. |
Sorry, something went wrong.
…thon#111862) * Split list_extend() into two sub-functions: list_extend_fast() and list_extend_iter(). * list_inplace_concat() no longer has to call Py_DECREF() on the list_extend() result, since list_extend() now returns an int.
…thon#111862) * Split list_extend() into two sub-functions: list_extend_fast() and list_extend_iter(). * list_inplace_concat() no longer has to call Py_DECREF() on the list_extend() result, since list_extend() now returns an int.
📚 Documentation preview 📚: https://cpython-previews--111862.org.readthedocs.build/