2 ms·
They do sort out dead batteries [1]. But pretty much every case you've listed is not exactly dead, but more like a philosophical disagreement. For example some
by lifthrasiir 4y ago
They do sort out dead batteries [1]. But pretty much every case you've listed is not exactly dead, but more like a philosophical disagreement.
For example some modules are not what they seem to be; graphlib doesn't purport to be a general graph library and statistics doesn't mean to replace scipy. They are just groups for otherwise independent bits of code, named so that similar future code can be grouped together. In some cases you have a waaaaaay too high threshold for "unused" modules, for example [1] kept getopt because it mirrors a popular C library.
[1] https://peps.python.org/pep-0594/ https://peps.python.org/pep-0594/
- eterevsky 4y ago> kept getopt because it mirrors a popular C library It's an excellent reason to keep it as a separately maintained module. Having in the standard library two modules for the same purpose just adds to the confusion.