Post Syndicated from original https://lwn.net/Articles/877957/rss

Feature deprecations are often controversial, but many projects find it
necessary, or desirable, to lose some of the baggage that has accreted over
time. A mid-November request to get rid of three Python standard library
modules provides a case in point. It was initially greeted as a good idea
since the modules had been officially deprecated starting with
Python 3.6; there are better ways to accomplish their
tasks now. But, of course, removing a module breaks any project that uses
it, at least without the project making some, perhaps even trivial,
changes. The cost of that is not insignificant, and the value in doing so
is not always clear, which led to higher-level conversation about deprecations.