On Tue, Jul 16, 2013 at 12:52 PM, Zygmunt Bazyli Krynicki <[email protected]> wrote: > > Mocker and mock are totally different. Mock is in stdlib since 3.3 so it is > likely the future but I found mocker easier to use and understand (I'm also > the current maintainer for mocker, if inactive a bit). > > As for nose/py.test: both are a bit non standard. I would strongly recommend > that you use unittest2, the python 2.x backport of updated stdlib test > stuff. It has a lot of compatible extensions. Python.test and nose have > those too but 1) they are not compatible 2) IMHO there is no advantage over > stock stuff _anymore_ > > Lastly Django is a bit of a different story but it gets healthier lately. > Strongly recommend to track what key upstream devs are doing there and why. > It will likely be in next django release and if you choose badly you'll > drift apart from other projects. > > Quick question: do you have a list of requirements?
No, nothing special I would say or that pops out of my mind at this moment. I would prefer to use what is available in Python by "default" - unittest and mock. I never considered unittest2 though, that is a good catch. Ciao. -- Milo Casagrande | Automation Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
