FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

gh-92888: memory_ass_sub() calls CHECK_RELEASED_INT() twice by vstinner · Pull Request #93127 · python/cpython · GitHub

/ cpython Public

gh-92888: memory_ass_sub() calls CHECK_RELEASED_INT() twice - #93127

Closed
vstinner wants to merge 1 commit into
python:mainfrom
vstinner:release_view
Closed

gh-92888: memory_ass_sub() calls CHECK_RELEASED_INT() twice#93127
vstinner wants to merge 1 commit into
python:mainfrom
vstinner:release_view

Conversation

Copy link
Copy Markdown
Member

If a memoryview is released while setting an item, raise an
exception. For example, converting an object to an index in C can
execute arbitrary Python code which can indirectly release the
memoryview.

If a memoryview is released while setting an item, raise an
exception. For example, converting an object to an index in C can
execute arbitrary Python code which can indirectly release the
memoryview.

Copy link
Copy Markdown
Member Author

I chose to keep the CHECK_RELEASED_INT() call at memory_ass_sub() entry.

I guess that memory_subscript() suffers from the same issue: I would prefer to fix it in a separated PR, but maybe then we can combine the two changes when backporting to stable branches.

Copy link
Copy Markdown
Member Author

PR #92946 seems more complete, I close my issue.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL