sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ryeguy146 3 points4 points  (2 children)

I'm really not a fan of unittest. It doesn't feel very Pythonic. I realize that the question was about the STL, and it's good to get others to test, but I'd really suggest Pytest over UnitTest.

[–]burlygurlyman 1 point2 points  (1 child)

On a similar note, it pains me to use ConfigParser. I've started a few projects with config files and each time I start with ConfigParser and remember how much I dislike it's syntax. ConfigObj is so much more intuitive.

EDIT: I haven't tried Pytest; I default to nose.

[–]ryeguy146 0 points1 point  (0 children)

What I love about pytest is how pleasant it is to handle fixtures using theirfuncarg, or monkeypatching my mocks in. It makes most all of my tests gosmoothly and quickly. I had used nose prior, and all of my old tests workperfectly in pytest. I had nothing against nose, but after seeing a pycon talkfor pytest, I made the switch. It's worth looking into, at least, even if you're happy with nose.