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/8e8307d70bb9dc18cfeeed3277c076309b275...
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.
Another idea:
* Stop suppressing DeprecationWarning by default
* Use at least one PendingDeprecationWarning and one DeprecationWarning.
* More than two PendingDeprecationWarning periods is preferred.
How do you think?
--
Inada Naoki