News for hackers. Stuff that matters.
Re:Myths of Enterprise Python by arethuza on Tuesday March 24, 2015 @10:25AM (#9256748)
Shouldn't you be writing tests anyway?

NB I'm not being flippant - I've been using Python for a couple of years and appreciate the lack of boilerplate compared to many other languages and if there are "type" problems my unit tests, which I will be writing anyway, find them. Using an IDE like PyCharm does a good job of warning you about type problems at development time so I don't have a lot of run time type problems.

Re:Myths of Enterprise Python by Retra on Tuesday March 24, 2015 @11:09AM (#9257040)
Yeah, you should, but you don't have to check trivial things like "is this a list?"
Re:Myths of Enterprise Python by arethuza on Tuesday March 24, 2015 @11:14AM (#9257081)
Well, I wouldn't write a unit test for that - I would write a unit test for the high level observable behavior and if I get it wrong that something is a list then it'll break and my unit test will fail.
Re:Myths of Enterprise Python by viraptor on Tuesday March 24, 2015 @01:26PM (#9258015)
I think that's closer to functional testing than unit testing though...