[issue34940] Possible assertion failure due to _check_for_legacy_statements()

Serhiy Storchaka added the comment: Seems failure is not possible here, but it is safer to always check for errors. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.6, Python 3.7 ___ Python

[issue34940] Possible assertion failure due to _check_for_legacy_statements()

Serhiy Storchaka added the comment: New changeset a4b48f194a131bad6fe1fcfb1f90ae2029304735 by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-34940: Fix the error handling in _check_for_legacy_statements(). (GH-9764)

[issue34940] Possible assertion failure due to _check_for_legacy_statements()

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9151 stage: -> patch review ___ Python tracker ___ ___

[issue34940] Possible assertion failure due to _check_for_legacy_statements()

New submission from Zackery Spytz : The PyUnicode_Tailmatch() and PyUnicode_FromString() calls in _check_for_legacy_statements() are not properly checked for failure. -- components: Interpreter Core messages: 327379 nosy: ZackerySpytz priority: normal severity: normal status: open