3 ms·
I was recently deciding which to use in a small project: unittest, pytest or nose. My default starting point is to prefer the standard library for assumed parti
by a3n 10y ago
I was recently deciding which to use in a small project: unittest, pytest or nose. My default starting point is to prefer the standard library for assumed participation and for longevity, but also to use 3rd party if there's a good reason or a clear consensus.
While looking at nose, I ran across this: https://nose.readthedocs.io/en/latest/ https://nose.readthedocs.io/en/latest/
> Note to Users: Nose has been in maintenance mode for the past several years and will likely cease without a new person/team to take over maintainership. New projects should consider using Nose2, py.test, or just plain unittest/unittest2.
That made me not want to investigate nose any further, and I decided I had to just decide and move on, and chose unittest. The suggestion to use unittest in the Note helped make that easier.
Maybe next time I'll use pytest, but I think the issue in the Note will dissuade me from using nose unless it's resolved.