Tim Peters wrote:
>
> I pay no attention to "backwards compatibility" issues in the libraries we
> ship, and have Guido's blessing for that ornery attitude: the libs we ship
> should do the best possible job in the context of the release they're
> shipped in. It's explicitly not a PythonLabs goal that people be able to
> pick modules out of a release and use them in an earlier release (although
> it may be a goal of some developers for some modules -- but then the burden
> is on them to ensure it works for the module and release combinations they
> care about).
As one of the frequent ranters about compatibility issues, I thoroughly
endorse this approach WRT "batteries included" as long as the APIs stay
the same.
--
--- Aahz (@pobox.com)
Hugs and backrubs -- I break Rule 6 <*> http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista
We must not let the evil of a few trample the freedoms of the many.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4