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.
https://nose.readthedocs.io/en/latest/#python3
nose supports python3. Building from source on python3 requires distribute. If you don’t have distribute installed, python3 setup.py install will install it via distribute’s bootstrap script. Additionally, if your project is using 2to3, python3 setup.py nosetests command will automatically convert your sources with 2to3 and then run the tests with python 3.
nose supports python3. Building from source on python3 requires distribute. If you don’t have distribute installed, python3 setup.py install will install it via distribute’s bootstrap script.
Additionally, if your project is using 2to3, python3 setup.py nosetests command will automatically convert your sources with 2to3 and then run the tests with python 3.
nose is deprecated or was removed in many of Linux distros, e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1797603 https://fedoraproject.org/wiki/Changes/DeprecateNose
nose
possible fix: Pytest's plugin similar to FreeIPA's one: https://pagure.io/freeipa/c/0cb12f3cdef899df47e749ddaef937f7d1bd7a91 (https://pagure.io/freeipa/issue/4610)
The question is about status of mod_nss project itself, is it deprecated/maintained? I asked because the migration from nose may require some nonzero effort.
I suppose the fair answer is "poorly maintained". I've only done reactive changes for a while now, like porting to OpenSSL 3. The last release was four years ago. It is effectively dead.
I don't have any handle on how many people still use it. I keep it alive mostly because RHEL 6 and RHEL 7.0-7.3 are still in the wild and they use mod_nss.
I used to re-sync with the mod_ssl code every year or so but by now the divergence is so great I fear it'd be like starting over.
I honestly don't know if it's worth porting the tests or not. Not doing so would mean risk of regressions if some future change is needed. I can't tell how likely that would be.
Metadata Update from @rcritten: - Custom field type adjusted to None
@rcritten, thank you. Yeah, it's pointless to port the tests then.