This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients christian.heimes, corona10, gvanrossum, kumaraditya, miss-islington, sobolevn, vstinner
Date 2022-02-24.17:04:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645722281.54.0.12131083909.issue46430@roundup.psfhosted.org>
In-reply-to
Content
> How it should be handled? Currently PyUnicode_InternInPlace ignores any errors and does not return it. It would be backwards-incompatible to change that, moreover as I explained in https://github.com/python/cpython/pull/30683#discussion_r800648477 intern_strings only check if all the items are strings which will be always true in case of deep-freeze so I don't think anything needs to be changed here. I would be interested to know if I am missing something though.

The other functions you are calling *do* return errors. You should not ignore those. If any errors are reported the caller can decide what to do (e.g. call Py_FatalError().
History
Date User Action Args
2022-02-24 17:04:41gvanrossumsetrecipients: + gvanrossum, vstinner, christian.heimes, corona10, miss-islington, sobolevn, kumaraditya
2022-02-24 17:04:41gvanrossumsetmessageid: <1645722281.54.0.12131083909.issue46430@roundup.psfhosted.org>
2022-02-24 17:04:41gvanrossumlinkissue46430 messages
2022-02-24 17:04:41gvanrossumcreate