You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Convert warnings to SyntaxWarning in parser #72215
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2017-10-23.12:58:50.126>created_at=<Date2016-09-08.19:23:04.700>labels= ['interpreter-core', 'type-feature', '3.7']
title='Convert warnings to SyntaxWarning in parser'updated_at=<Date2017-10-23.12:58:50.124>user='https://github.com/serhiy-storchaka'
AST parser converts UnicodeError and ValueError raised during parsing string literal to SyntaxError. Maybe make it converting warnings (see bpo-27364) to SyntaxWarning?
I think it would be best to solve this issue, solving both bpo-28128 and any future warning-introducing feature or deprecation. I've marked this issue as a dependency for bpo-28128 as well as upping the priority. There are less than 7 weeks before the final 3.6.0 release and I would like to get as much mileage out of this before then.
Activity
serhiy-storchaka commentedon Sep 8, 2016
AST parser converts UnicodeError and ValueError raised during parsing string literal to SyntaxError. Maybe make it converting warnings (see bpo-27364) to SyntaxWarning?
Vgr255 commentedon Oct 29, 2016
Cross-ping from bpo-28128
I think it would be best to solve this issue, solving both bpo-28128 and any future warning-introducing feature or deprecation. I've marked this issue as a dependency for bpo-28128 as well as upping the priority. There are less than 7 weeks before the final 3.6.0 release and I would like to get as much mileage out of this before then.
Thanks :)
serhiy-storchaka commentedon Oct 23, 2017
Closed because I don't see ways to do this.