-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Antoine Pitrou wrote: > There is always the possibility that a new feature breaks existing code, for > example because it relies on a similarly named attribute, or on some obscure > internal condition. I think this should be qualified so that it only applies > when e.g. a fair number of third-party apps or libraries are broken. I think the recent asyncore changes are a good test case here: they broke major consumers of the package (Zope, supervisord), but it wasn't obvious that the breakage would occur, because the API of the package wasn't clear: the apps broken by the change were forced to rely on stuff that the subsequent maintainer considered "implementation details." Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKO88q+gerLs4ltQ4RAmmkAJ4ghgszBWGruCqONtouAXp82G+blgCgySsL 4ywgpU5137D5isiJ8+d6KtM= =OksB -----END PGP SIGNATURE-----
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