3 ms·
Comment on the post links to https://github.com/nose-devs/nose/issues/11 https://github.com/nose-devs/nose/issues/11 which reported the issue in 2011. Ugh.
by js2 11y ago
Comment on the post links to https://github.com/nose-devs/nose/issues/11 https://github.com/nose-devs/nose/issues/11 which reported the issue in 2011. Ugh.
- bobwaycott 11y agoThat is deceptive, as it is a mirrored issue from when the project was brought to Github (which is why it reads so oddly, all from the same author). It'd been reported nearly 20 months prior on googlecode: https://code.google.com/p/python-nose/issues/detail?id=335 https://code.google.com/p/python-nose/issues/detail?id=335 This issue has been open since April 2010. What a shame.