[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset a2f1be0b5ba2bed49b7f94c026b541ff07e52518 by Serhiy Storchaka (Miss Islington (bot)) in branch '2.7': bpo-15606: Improve the re.VERBOSE documentation. (GH-4366) (#4395)

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset 14c1fe682f0086ec28f24fee9bf1c85d80507ee5 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': bpo-15606: Improve the re.VERBOSE documentation. (GH-4366) (#4394)

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Roundup Robot : -- pull_requests: +4343 ___ Python tracker ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Roundup Robot : -- pull_requests: +4342 ___ Python tracker ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset b0b44b4b3337297007f5ef87220a75df204399f8 by Serhiy Storchaka in branch 'master': bpo-15606: Improve the re.VERBOSE documentation. (#4366)

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: Steven's patch is outdated since 71a0b43854164b6ada0026d90f241c987b54d019. But that commit missed that spaces are not ignored within tokens. PR 4366 fixes this by using the wording from Ezio's comments. -- nosy:

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Serhiy Storchaka : -- pull_requests: +4319 stage: needs patch -> patch review ___ Python tracker ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Kevin Shweh added the comment: It looks to me like there are more situations than the patch lists where whitespace still separates tokens. For example, *? is a reluctant quantifier and * ? is a syntax error, even in verbose mode. -- nosy: +Kevin Shweh

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: Steven, would you mind to update your patch according to review comments and create a pull request on GitHub? -- stage: patch review -> needs patch versions: +Python 2.7, Python 3.6, Python 3.7 -Python 3.3

[issue15606] re.VERBOSE whitespace behavior not completely documented

Ezio Melotti added the comment: See also #17184. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15606 ___ ___ Python-bugs-list mailing list

[issue15606] re.VERBOSE whitespace behavior not completely documented

Changes by Roy Smith r...@panix.com: -- nosy: +roysmith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15606 ___ ___ Python-bugs-list mailing list

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: See also related issue11204. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15606 ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Changes by Ezio Melotti ezio.melo...@gmail.com: -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15606 ___ ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Steven Collins added the comment: Fair enough, but in that case I still think the current behavior should be documented. Attached is a possible patch. (This is my first interaction with the Python issue tracker, by the way; apologies if I ought to have set some field differently or left some