3 ms·
> FWIW, the Python developers have wanted to drop the cgi module for over 20 years. It has no maintainer. It works. Does it need a maintainer? The point isn't
by guappa 3y ago
> FWIW, the Python developers have wanted to drop the cgi module for over 20 years. It has no maintainer.
It works. Does it need a maintainer?
The point isn't how to replace them. The point is that I have stuff that works and has been working for several years and will stop working.
- eesmith 3y agoThen Python is not the language for you, and never has been. The Python core developers have had a practice of removing standard library packages for over 30 years, including packages that - like cgi.py - worked. For example, modules removed with Python 2.0 included cmp, cmpcache, dircmp, dump, find, grep, packmail, poly, stdwin, util, whatsound, and zmod. Python 2.4 removed mpz, rotor, and xreadlines - no more Enigma machine emulation for you, and I had to change my code because I used xreadlines. Python 3.0 removed even more modules: cl, md5, sha, rfc822, and more. Plus it did some library reorganization. Ever use the "parser" module? I did. It was removed in 3.10 because of the switch to the PEG parser. PEP 594 re-affirms the reasoning behind the long-given practice removing old packages. There are language communities with a stronger commitment to not breaking old code. COBOL is fantastically backwards compatible, for an obvious example. I urge you to consider the options I gave. The functionality you want can be done using the standard library without that much effort.