On Tue, 11 May 2021 10:25:38 +0200 Petr Viktorin <encu...@gmail.com> wrote: > On 10. 05. 21 10:53, Inada Naoki wrote: > > Hi, folks. > > > > Now Python 3.11 development is open and I am removing some deprecated > > stuffs carefully. > > > > I am considering `configparser.ParseError.filename` property that is > > deprecated since Python 3.2. > > https://github.com/python/cpython/blob/8e8307d70bb9dc18cfeeed3277c076309b27515e/Lib/configparser.py#L315-L333 > > > > My random thoughts about it: > > > > * It has been deprecated long enough. > > * But the maintenance burden is low enough. > > * If we don't remove long deprecated stuff like this, Python 4.0 will > > be a big breaking change. > > > > My proposal: > > > > * Change DeprecationWarning to FutureWarning and wait one more version. > > * DeprecationWarning is suppressed by default to hide noise from end > > users. > > * But sudden breaking change is more annoying to end users. > > > > I am not proposing to change PEP 387 "Backwards Compatibility Policy". > > This is just a new convention. > > Test tools should treat DeprecationWarning as error by default [0][1]. > So even if end users don't really see it, I don't consider it "hidden".
Several data science libraries emit FutureWarning rather than DeprecationWarning for the reason that DeprecationWarning is silenced by default. So, yes, it is a real problem. Regards Antoine. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/HSGO5IUNNRDXO2U26UMXXIMJJDWTCYYA/ Code of Conduct: http://python.org/psf/codeofconduct/
