Future of nose and issues for scikit-image
Dear devs, I would like to raise a potential issue with our test suite. Let me list the facts. Our tests rely on nose. As you may have seen, we often have deprecation warnings (See https://github.com/scikit-image/scikit-image/issues/2414 ). These warnings come from nose, https://github.com/nose-devs/nose/issues/929 a ticket opened in Jun '15. Tom Caswell opened a PR in Sept '15 https://github.com/nose-devs/nose/pull/952 that got only little attention. In another of our issues, some tests are not run (those in directories starting by an underscore). https://github.com/scikit-image/scikit-image/issues/2127 As stated in our issue, it is hard-coded in nose and WON'T be fixed. Upstream suggests to upgrade to nose2. Egor investigated this possibility but it sounds not possible (Egor, can you elaborate?) It seems clear that nose is not maintained any more (last commit, 10 months ago, last release June '15). The deprecation warning we have will turn to a broken code with python 3.6 that has just been released. I let you check that my interpretation is correct, but to me, it represents a major issue for scikit-image. Feel free to comment and to correct me if necessary. I'm not well-experienced with the different libraries for unittesting. Best, -- François Boulogne. http://www.sciunto.org GPG: 32D5F22F
Hello, Both matplotlib and sklearn are moving away from nose. I think sklearn's way of moving away is both very sustainable and the transition has been very smooth. The standard library unittest has been wrapped such that the API remains with nose/numpy.testing in a utils.testing module. That means the test suite needs very little modification, and we kept nose's very nice API. We still use nosetests as our test runner. If scikit-image decides to move forward into that direction, I'd be happy to help with the transition. Cheers, N On 30 December 2016 at 13:26, François Boulogne <fboulogne@sciunto.org> wrote:
Dear devs,
I would like to raise a potential issue with our test suite. Let me list the facts.
Our tests rely on nose. As you may have seen, we often have deprecation warnings (See https://github.com/scikit-image/scikit-image/issues/2414 ). These warnings come from nose, https://github.com/nose-devs/nose/issues/929 a ticket opened in Jun '15. Tom Caswell opened a PR in Sept '15 https://github.com/nose-devs/nose/pull/952 that got only little attention.
In another of our issues, some tests are not run (those in directories starting by an underscore). https://github.com/scikit-image/scikit-image/issues/2127 As stated in our issue, it is hard-coded in nose and WON'T be fixed. Upstream suggests to upgrade to nose2. Egor investigated this possibility but it sounds not possible (Egor, can you elaborate?)
It seems clear that nose is not maintained any more (last commit, 10 months ago, last release June '15). The deprecation warning we have will turn to a broken code with python 3.6 that has just been released.
I let you check that my interpretation is correct, but to me, it represents a major issue for scikit-image. Feel free to comment and to correct me if necessary. I'm not well-experienced with the different libraries for unittesting.
Best,
-- François Boulogne. http://www.sciunto.org GPG: 32D5F22F
_______________________________________________ scikit-image mailing list scikit-image@python.org https://mail.python.org/mailman/listinfo/scikit-image
participants (2)
-
François Boulogne -
Nelle Varoquaux