Steve Holden <steve at holdenweb.com> 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
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