Re:Myths of Enterprise Python
by crdoconnor on Tuesday March 24, 2015 @12:04PM
(#9257453)
>Less than that, in my experience. Certainly a lot less than the amount of tests and documentation you'd need to make up for the absence of types.
Certainly more, in my experience.
>You need to work with the language. Is a python test cycle faster than a full rebuild? Probably.
By an order of magnitude.
> Is it faster than the time between making a change and seeing the red underline in one's IDE?
It can be that quick, yes. I have a unit test watcher that reruns them every time a file save in the project is detected (using watchdog/epoll), and I get the results back in seconds.
That has the added advantage of detecting more than just trivial type errors. It catches logic errors too.
Less than that, in my experience. Certainly a lot less than the amount of tests and documentation you'd need to make up for the absence of types.
> I found the complaint that it finds bugs earlier (at compilation time!) ironic given that, in my experience, running a suite of unit tests takes less time in python than, say, compiling does in Java, never mind compiling and running tests.
You need to work with the language. Is a python test cycle faster than a full rebuild? Probably. Is it faster than the time between making a change and seeing the red underline in one's IDE? Absolutely not, in my experience.