News for hackers. Stuff that matters.
Re:Navigating the Postmodern Python World by nostrademons on Friday July 12, 2013 @02:51AM (#6031276)
What's your test coverage? It's usually not that hard to reach 100% if you have a decent coverage analyzer. Or even if you don't - one easy way is to never write a line of code unless you have a failing test that exercises it.

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.

Re:Navigating the Postmodern Python World by bsaul on Friday July 12, 2013 @03:52AM (#6031425)
My unit tests did catch it, but if you've ever (seriously) coded in a statically typed language, you really like to have those errors show almost as you type.

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).

Re:Navigating the Postmodern Python World by nostrademons on Friday July 12, 2013 @12:20PM (#6033432)
There's nothing that prevents an IDE from running all the tests associated with a project and then highlighting the line numbers of any exceptions that get thrown. Infinitest will do this for Java in Eclipse and IntelliJ, though I don't think it works with Python.

http://infinitest.github.io/

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.

Re:Navigating the Postmodern Python World by zcrar70 on Friday July 12, 2013 @04:26PM (#6034976)
"whip up a vimscript"...