[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Raymond Hettinger added the comment: Thank you for closing this. I think it would only add clutter to a module that is already puts readers into information overload. -- nosy: +rhettinger ___ Python tracker

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Eli Bendersky added the comment: I think we have enough < 0 to reject the issue. Closing. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ _

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Éric Araujo added the comment: I had too the need to find out the value to pass when there are no flags, so a mention of 0 in the doc would have been enough for me. -0 on a new constant. -- ___ Python tracker __

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Ezio Melotti added the comment: If you want to provide no flags, I think it's easier to provide no flags, rather than having to learn some NOFLAGS constant value that can be used to make the fact that you are passing no flags more explicit than it already is. I might agree that ORing flags mig

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Eli Bendersky added the comment: Antoine, what's the outcome of people wondering about the difference? I don't see what's bad about it, it's not as if people are writing (or supposed to write) code that does arithmetic on these flag values. Their only usage is to: 1. Provide no flags 2. Provi

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Ezio Melotti added the comment: I think a proper solution would be fixing #11957. Adding a NOFLAGS alias for 0 would help fixing #12875, but I don't think it will be useful/use otherwise. -- ___ Python tracker _

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Antoine Pitrou added the comment: As Eric, I don't really think it's useful, and it might actually be confusing (people will start wondering if there's a difference between 0 and NOFLAGS). -- nosy: +pitrou ___ Python tracker

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Eric V. Smith added the comment: Since the flags are OR'd together, I don't see what other value the "no flags" parameter could have, other than zero. That said, I don't feel strongly about it, and if it helps readability I'm not opposed. -- ___ Py

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

New submission from Eli Bendersky : The flags 're' accept are numeric underneath, and the current value of "no flags" is just 0, which is also specified in the documentation as the default value. However, using raw numeric values is not a good programming practice. The suggestion is to add a