3 ms·
> There was a claim it couldn't go into 2.7 because it was an API change (even though it was backwards compatible) But it was not backwards compatible. "It wor
by dozzie 9y ago
> There was a claim it couldn't go into 2.7 because it was an API change (even though it was backwards compatible)
But it was not backwards compatible. "It works in 2.7" does not mean it works
in 2.7.8, but if you try using 2.7.7 it falls apart.
- js2 9y agoBackwards compatible means the patch adds new functionality without breaking the API for existing programs. Of course the new functionality would only work in whichever release it was first shipped. Maybe you’re objecting to it being introduced in a 2.7.x patch release, but that's not without precedent for Python. For example, https://bugs.python.org/issue22960 https://bugs.python.org/issue22960 added a new optional argument to xmlrpclib.ServerProxy and was introduced in 2.7.9.