-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-42924: Fix incorrect copy in bytearray_repeat #24208
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
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add also tests.
Misc/NEWS.d/next/Core and Builtins/2021-01-13-14-06-01.bpo-42924._WS1Ok.rst
Outdated
Show resolved
Hide resolved
The base case is already tested via `test_repeat` and `test_repeat_1char`.
Thanks for the comments, those should be addressed now. I hope the test case is in the right place ( |
Thanks @TobiasHoll for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Before, using the * operator to repeat a bytearray would copy data from the start of the internal buffer (ob_bytes) and not from the start of the actual data (ob_start). (cherry picked from commit 61d8c54) Co-authored-by: Tobias Holl <TobiasHoll@users.noreply.github.com>
GH-24211 is a backport of this pull request to the 3.9 branch. |
Before, using the * operator to repeat a bytearray would copy data from the start of the internal buffer (ob_bytes) and not from the start of the actual data (ob_start). (cherry picked from commit 61d8c54) Co-authored-by: Tobias Holl <TobiasHoll@users.noreply.github.com>
GH-24212 is a backport of this pull request to the 3.8 branch. |
Before, using the * operator to repeat a bytearray would copy data from the start of the internal buffer (ob_bytes) and not from the start of the actual data (ob_start).
Before, using the * operator to repeat a bytearray would copy data from the start of the internal buffer (ob_bytes) and not from the start of the actual data (ob_start). (cherry picked from commit 61d8c54) Co-authored-by: Tobias Holl <TobiasHoll@users.noreply.github.com>
Before, using the * operator to repeat a bytearray would copy data from the start of the internal buffer (ob_bytes) and not from the start of the actual data (ob_start). (cherry picked from commit 61d8c54) Co-authored-by: Tobias Holl <TobiasHoll@users.noreply.github.com>
This should fix bpo-42924.
Before, using the
*
operator to repeat abytearray
would copy data from the start of the internal buffer (ob_bytes
) and not from the start of the actual data (ob_start
). The assert in this example used to fail, now it should pass.https://bugs.python.org/issue42924