STINNER Victor <vstin...@redhat.com> added the comment:
> As a particularly relevant example, we currently have 3 different > "warnoptions" fields: the private-to-main one for reading the command line > settings, the "wchar_t *" list in the core config, and the "PyObject *" list > object in the main interpreter config (which is also the one aliased as > sys.warnoptions). This issue has been fixed in bpo-36763 with the implementation of the PEP 587. PyConfig.warnoptions is now an unified list of warnings options. Moreover, the priority of warnings options is now defined at: https://www.python.org/dev/peps/pep-0587/#priority-and-rules ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33135> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
