You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently nose will soon cease to work for setuptools; while that doesn't directly affect i18nspector, the end is nigh for it in Debian as well, and it's obviously my preference to keep running build-time and autopkgtest tests on i18nspector.
Is there a plan to migrate to a different test harness? The migration looks moderately painful but certainly doable to either unittest or py.test (the latter probably being easier).
The text was updated successfully, but these errors were encountered:
Apparently nose will soon cease to work for setuptools; while that doesn't directly affect i18nspector, the end is nigh for it in Debian as well, and it's obviously my preference to keep running build-time and autopkgtest tests on i18nspector.
Is there a plan to migrate to a different test harness? The migration looks moderately painful but certainly doable to either unittest or py.test (the latter probably being easier).
Maintaining a nose fork (in a life-support style) would be probably less work than migrating away from it, but I'm not excited about either.
For now, I sent patches to the Debian bug. Let's see how it goes.
Apparently
nose
will soon cease to work forsetuptools
; while that doesn't directly affect i18nspector, the end is nigh for it in Debian as well, and it's obviously my preference to keep running build-time and autopkgtest tests on i18nspector.https://lists.debian.org/debian-python/2021/10/msg00058.html
Is there a plan to migrate to a different test harness? The migration looks moderately painful but certainly doable to either
unittest
orpy.test
(the latter probably being easier).The text was updated successfully, but these errors were encountered: