3 ms·
My first thought was "who's still using CGI?" then I read the docs: > Deprecated since version 3.11, will be removed in version 3.13
by parhamn 2y ago
My first thought was "who's still using CGI?" then I read the docs:
> Deprecated since version 3.11, will be removed in version 3.13
- dec0dedab0de 2y agoim surprised it made it anywhere in 3.x
- zahlman 2y agoI'm not. Python takes great strides to ensure backwards compatibility - because there's seemingly endless demand for it. Keep in mind 2.7 got a patch months after its planned EOL, which was already extended an extra 5 years from the regular release schedule, and major projects like Pip maintained support for well beyond that point, and people still complained. There's significant hysteresis in the project: a strong reluctance to remove things that they would never even remotely consider adding today if they didn't already exist. After all: if it already exists, someone might still be using it (and it's harder to gather that kind of information, the older the thing in question is); but adding it new would create a maintenance burden (never mind that the old rarely-used stuff doesn't really get maintained).