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
C/API documentation: request for documentation of change to Py_ssize_t* arguments. #48379
Comments
In general, the Python C/API manual is very careful to document when However, there is a group of changes that are not documented. In Python I suggest that a note is added to the documentation of all functions Best regards Jakob |
I think the Py_ssize_t change is clearly documented in the "What's new" Didn't you get any compilation warning? I suggest to use a newer version of Scientific Python: 2.7 at least uses |
Don't get me wrong: I am not complaining about the code breakage, it is |
I don't think that we will change the 2.5 manuals anymore; Python 2.5 is For 2.6, I suppose contributions would be welcome. |
I agree with Martin. Patches are welcome. |
How does this look as an initial idea? |
Why not use .. versionchanged? |
Pure ignore. Let me adjust the patch. Do we prefer versionchanged before |
Committed a first batch in r71910. |
Fixed the slice stuff in r71915. |
OK, I went through the entire C API documentation and marked up every |
Merged 2.6 and py3k what was appropriate. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: