[issue6650] sre_parse contains a confusing generic error message

Changes by Serhiy Storchaka : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue6650] sre_parse contains a confusing generic error message

Serhiy Storchaka added the comment: Current (after issue22364) error message is: >>> re.match('(?.*)', 'foo') Traceback (most recent call last): ... sre_constants.error: unknown extension ? ___ ___

[issue6650] sre_parse contains a confusing generic error message

Serhiy Storchaka added the comment: And of course we shouldn't use just %s. source.next can be non-printable character. -- ___ Python tracker ___

[issue6650] sre_parse contains a confusing generic error message

Serhiy Storchaka added the comment: May be. We should compare with regex and perhaps add a test. -- assignee: -> serhiy.storchaka nosy: +ezio.melotti, pitrou ___ Python tracker _

[issue6650] sre_parse contains a confusing generic error message

Éric Araujo added the comment: Serhiy: I meant that the patch looks right to me (“I would apply it”), not that I intended to do it (“I will apply it”)—I’m not set up right now to contribute to CPython again. Would you mind committing it? (Edited versions: exception messages are not part of a

[issue6650] sre_parse contains a confusing generic error message

Changes by Serhiy Storchaka : -- assignee: -> eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue6650] sre_parse contains a confusing generic error message

Changes by Petri Lehtinen : -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6650] sre_parse contains a confusing generic error message

Éric Araujo added the comment: In the absence of better propositions, the message in the patch seems more helpful to me than the previous, especially because “lookbehind” is a search term that matches <0.1 wink> on docs.python.org. So I’d apply this patch. -- nosy: +merwok __

[issue6650] sre_parse contains a confusing generic error message

Torne Wuff added the comment: I suspect a better message could be invented, but I'm not sure what :) -- ___ Python tracker ___ ___ Pyt

[issue6650] sre_parse contains a confusing generic error message

Daniel Diniz added the comment: Thanks for the patch, LGTM assuming we don't need a test for this. Do you think the vague message could be less cryptic for users that didn't want lookbehind (or don't know what it is)? -- nosy: +ajaksu2 priority: -> low stage: -> patch review version

[issue6650] sre_parse contains a confusing generic error message

New submission from Torne Wuff : sre_parse raises an exception with the message "syntax error" - very generic and confusing - in the case where something that looks like a lookbehind assertion is invalid. >>> import re >>> re.match('(?.*)', 'foo') Traceback (most recent call last): File "", li