Sorry, something went wrong.
Sorry, something went wrong.
|
@vstinner @corona10 @shihai1991 please review |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Sorry, something went wrong.
|
@vstinner would you please review? |
Sorry, something went wrong.
| } \ | ||
| if (PyDict_SetItemString(d, string, o) < 0) { \ | ||
| Py_DECREF(o); \ | ||
| goto error; \ |
There was a problem hiding this comment.
"return NULL;" is enough: you should remove the error label. An error label is used when you need to clean up things, it's not the case here. Same remark at the bottom of the file.
Sorry, something went wrong.
| return NULL; | ||
| } | ||
|
|
||
| static void *PyCurses_API[PyCurses_API_pointers]; |
There was a problem hiding this comment.
There are warnings on the PR, like ‘PyCurses_API’ defined but not used [-Wunused-variable].
Sorry, something went wrong.
|
https://bugs.python.org/issue1635741 is closed. What is the status of this PR? |
Sorry, something went wrong.
|
The change is still relevant, but should use a new issue number. Moreover, the SC asked to put the conversion of static types to heap types on hold. @encukou and @erlend-aasland wrote https://peps.python.org/pep-0687/ which may unblock the situation but it's still a draft. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Closing as per #101714 (comment). Thanks for the effort, Mohamed! |
Sorry, something went wrong.
https://bugs.python.org/issue1635741