Skip to content

Commit

Permalink
Add a note to users about the state of Nose.
Browse files Browse the repository at this point in the history
  • Loading branch information
@jszakmeister
jszakmeister committed Nov 4, 2015
1 parent 50a55f6 commit 0f40fa9
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions doc/index.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,15 @@
contain the root `toctree` directive.
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 <https://github.com/nose-devs/nose2>`_, `py.test
<http://pytest.org/>`, or just plain unittest/unittest2.


Installation and quick start
============================

Expand Down

3 comments on commit 0f40fa9

@mitya57
Copy link
Contributor

@mitya57 mitya57 commented on 0f40fa9 Nov 5, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is nose2 really better developed than nose? I see there even less activity than in this repository (i.e. last commit in June)…

@jszakmeister
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't honestly know. The activity level is low, but it is a much better code base. Besides, we agreed that Nose was going to be in maintenance mode, Nose2 was the way forward, and that was part of the reason I took over maintainership at all. Personally, I wasn't ever agreeing to help make Nose live forever--it was more of a fix critical bugs the best I could with the time that I had available. There's some serious deficiencies in the Nose code base that can only be fixed with a lot of TLC, and no one on the current team really has the energy to commit to it.

That is not a knock on anyone... Nose has been around a long time, has lived through several changes in unit testing mentality, and across a number of versions of Python. It's legacy and with that comes the cruft of organic growth. It's just way more than I can deal with alone.

@Jamim
Copy link

@Jamim Jamim commented on 0f40fa9 Oct 30, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related issue: #1092

Please sign in to comment.