Steve Holden <[EMAIL PROTECTED]> writes: > Yes, but unless I misunderstand you, you don't regard a mass > renaming of the module's functionality and removal of existing > aliases as a change to the API.
You slightly misunderstand me. The above changes *are* a change to the API, by definition. My position is that those changes, which *only* (and deliberately) change names without changing behaviour, are far below the threshold that might justify a new module. > As far as I'm concerned, if I have to alter my code to use the > updated module you have changed the API. Test code is particularly > sensitive to such changes. I agree entirely with this. -- \ “Smoking cures weight problems. Eventually.” —Steven Wright | `\ | _o__) | Ben Finney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
