-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats #3750
Comments
Please could you test with #3749? |
Of course I did a search for existing issues and didn't think to check for existing pull requests. It looks like the same issue, and the PR looks good to me (who is an absolute stranger to the Python C API). How do I pip install a github PR into a virtualenv to test? |
What I did was clone the repo, fetch the pull/3749 ref, check it out, and The deprecation warning is gone and all my tests pass. |
Thanks for the report and testing, #3749 has been merged and will be in Monday's 6.0.0 release. |
* Update unit tests, add support for running under tox * Update requirements.txt etc. also fix an error in one of the tests * Refactored har tests, they now work and should be clearer what they are trying to achieve * test_runner.py: fix * Fix for new python c api python-pillow/Pillow#3750
See python-pillow/Pillow#3750 . Thanks.
What did you do?
Ran my test suite on Python 3.8.0a3
What did you expect to happen?
The test to pass
What actually happened?
The tests did pass, but there were new deprecation warnings from Pillow:
These were introduced by https://bugs.python.org/issue36381 to warn about an upcoming Python C API change. The meaning of PY_SSIZE_T_CLEAN is described in https://python.readthedocs.io/en/stable/c-api/arg.html#strings-and-buffers.
What Pillow needs to do is:
make sure the type of the length argument is a Py_ssize_t
PY_SSIZE_T_CLEAN was introduced in Python 2.5 so there shouldn't be any backwards-compatibility issues.
What are your OS, Python and Pillow versions?
Reproduction
The text was updated successfully, but these errors were encountered: