Issue 34920: PYTHONWARNINGS entries are escaped (original) (raw)
Issue34920
Created on 2018-10-07 10:30 by nikratio, last changed 2022-04-11 14:59 by admin. This issue is now closed.
Messages (3) | ||
---|---|---|
msg327272 - (view) | Author: Nikolaus Rath (nikratio) * | Date: 2018-10-07 10:30 |
According to https://docs.python.org/3/library/warnings.html#describing-warning-filters: "The meaning of each of these fields [of PYTHONWARNINGS] is as described in ." The description of the "The Warnings filter" says "module is a string containing a regular expression that the module name must match." However, when parsing PYTHONWARNINGS, the warnings module explicitly escapes the module field. | ||
msg327276 - (view) | Author: Martin Panter (martin.panter) * ![]() |
Date: 2018-10-07 12:26 |
Déjà vu. Maybe duplicate of Issue 34624? | ||
msg327278 - (view) | Author: Nikolaus Rath (nikratio) * | Date: 2018-10-07 13:02 |
yes, this is a duplicate. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:59:06 | admin | set | github: 79101 |
2018-10-13 03:20:39 | martin.panter | set | status: open -> closedresolution: duplicatestage: resolved |
2018-10-07 13:02:05 | nikratio | set | messages: + |
2018-10-07 12:26:54 | martin.panter | set | superseder: -W option and PYTHONWARNINGS env variable does not accept module regexesmessages: + nosy: + martin.panter |
2018-10-07 10:30:17 | nikratio | create |