[issue28951] re.flags not documented in Module Contents as promised.

Change by Irit Katriel : -- keywords: +easy versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.6, Python 3.7 ___ Python tracker ___

[issue28951] re.flags not documented in Module Contents as promised.

Change by Serhiy Storchaka : Removed file: https://bugs.python.org/file45934/unnamed ___ Python tracker ___

[issue28951] re.flags not documented in Module Contents as promised.

Change by Serhiy Storchaka : Removed file: https://bugs.python.org/file45940/unnamed ___ Python tracker ___

[issue28951] re.flags not documented in Module Contents as promised.

Change by Serhiy Storchaka : -- components: +Regular Expressions nosy: +ezio.melotti, mrabarnett stage: -> needs patch versions: +Python 2.7, Python 3.6, Python 3.7 -Python 3.5 ___ Python tracker

[issue28951] re.flags not documented in Module Contents as promised.

Change by Serhiy Storchaka : Removed file: https://bugs.python.org/file45941/unnamed ___ Python tracker ___

[issue28951] re.flags not documented in Module Contents as promised.

R. David Murray added the comment: (Please delete the message you are replying to when responding to bug tracker emails.) I think a section heading would be good (three subheads under module contents: functions, flags, and exceptions). I'm less in favor of alphabetical entries for synonyms.

[issue28951] re.flags not documented in Module Contents as promised.

kevin added the comment: Oh, and on the alphabetized list, I suggest NOT listing synonyms together, but just mark some as "synonym for X" and listing them all alphabetically (according to "en" collation, not "C" so upper- and lower-case sort together, not separately). On Sat, Dec 17, 2016 at

[issue28951] re.flags not documented in Module Contents as promised.

kevin added the comment: Well, my original problem is that I wanted to find out what the flags did and could not find any pointer in the table of contents. I think they deserve either really good cross-references, or a heading in the contents. And a non-confusing alphabetized list, if they're

[issue28951] re.flags not documented in Module Contents as promised.

R. David Murray added the comment: Making a 'flags' subheading in module contents would be reasonable. Alternatively we could just drop that parenthetical, since the descriptions for each flag are themselves cross-linked. -- ___ Python tracker

[issue28951] re.flags not documented in Module Contents as promised.

kevin added the comment: Ordinarily when I see a cross-reference like that "the flags are described in foo" I expect foo to have a heading "FLAGS" so I can tell I'm looking at what was promised. Not knowing much about flags, it was not clear to me that those scattered lines re.A through re.X

[issue28951] re.flags not documented in Module Contents as promised.

R. David Murray added the comment: When I follow the link to module contents, I find a list of the flags with their descriptions. (re.A, re.I, etc, etc). Perhaps you are confusing the letters used in the regular expression to represent the flags with the flags themselves? I'm not sure how

[issue28951] re.flags not documented in Module Contents as promised.

New submission from kevin: In the online documentation of module re (https://docs.python.org/3.5/library/re.html) under 6.2.1. Regular Expression Syntax for item (?aiLmsux) we are promised "The flags are described in Module Contents" but no description is found there. In fact a number