Changing a function signature is the kind of thing that tests can & should catch. You need them anyway to catch edge cases in the logic and document the code, and then once you've done that you usually get pretty good coverage for free.
Changing a function signature is the kind of thing that tests can & should catch. You need them anyway to catch edge cases in the logic and document the code, and then once you've done that you usually get pretty good coverage for free.
To give you an example on how i do small refactoring in objective-c :
I change the function (or class) signature i know i need to change. I compile, then xcode shows me every single line of code i need to change.
Most of time, it shows me places i didn't remember also used that function (i'm talking "utils"-like functions).
Python has an unfortunate culture of "just an editor, please", so the main IDEs for it are light-years behind Java IDEs, but you could probably easily whip up a vimscript or .el that does this and highlights the line in the editor.