[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

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

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

miss-islington added the comment: New changeset cbcd2e36d6cbb1d8b6a2b30a2cf1484b7857e7d6 by Miss Islington (bot) in branch '3.9': bpo-39394: Improve warning message in the re module (GH-31988) https://github.com/python/cpython/commit/cbcd2e36d6cbb1d8b6a2b30a2cf1484b7857e7d6 --

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

miss-islington added the comment: New changeset 906f1a4a95e9ca82171a40a28b16533a14fa339c by Miss Islington (bot) in branch '3.10': bpo-39394: Improve warning message in the re module (GH-31988) https://github.com/python/cpython/commit/906f1a4a95e9ca82171a40a28b16533a14fa339c --

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Change by miss-islington : -- pull_requests: +30081 pull_request: https://github.com/python/cpython/pull/31990 ___ Python tracker ___

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +30080 pull_request: https://github.com/python/cpython/pull/31989 ___ Python tracker

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Serhiy Storchaka added the comment: New changeset 4142961b9f5ad3bf93976a6a7162f8049e354018 by Serhiy Storchaka in branch 'main': bpo-39394: Improve warning message in the re module (GH-31988) https://github.com/python/cpython/commit/4142961b9f5ad3bf93976a6a7162f8049e354018 --

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Serhiy Storchaka added the comment: This warning was introduced in 3.6. It is a time to convert it into an error. RE error messages contain position. But I understand that very few users will use 3.11 in nearest future, so I am going to add a position to warning message and backport this

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +30079 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31988 ___ Python tracker

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Mark Shannon added the comment: I have to admit that I find the truncated version more readable. Some sort of truncation is useful, as a regex could be thousands of character long. Adding the offset to the warning message seems like a useful addition. -- nosy: +Mark.Shannon

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Jürgen Gmach added the comment: > Why do you want to output the full regular expression? The current output gives no clue about which flag is problematic, nor does it show the complete output (which at least would include the problematic flag), nor does it show the exact line, as it refers

[issue39394] re: DeprecationWarning for `flag not at the start of expression` is cutoff too early

Change by STINNER Victor : -- title: DeprecationWarning for `flag not at the start of expression` is cutoff too early -> re: DeprecationWarning for `flag not at the start of expression` is cutoff too early ___ Python tracker