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
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.
I think this project should have a similar note about the status of django-nose.
Personally, I no longer use django-nose on my work projects (I'm a happy convert to pytest), which means I do not have a working project for testing the project, finding issues, and confirming changes. In addition, I've had less and less time and energy for the work of open source maintenance. I'm sorry that this has impacted this project.
My hope with migrating to jazzband is that it would be easier for the users of the project to identify themselves and take over maintenance. I think a clear statement in the project README would help this along.
Here's my first draft:
Note to users:
Nose has been in maintenance mode since at least 2015. django-nose is in maintenance mode as well, and the sole maintainer is no longer an active user. See https://jazzband.co to learn how django-nose is maintained and how you can help. New projects should consider using py.test, or unittest with the Django testing framework.
The text was updated successfully, but these errors were encountered:
The nose docs have this note:
I think this project should have a similar note about the status of
django-nose
.Personally, I no longer use
django-nose
on my work projects (I'm a happy convert to pytest), which means I do not have a working project for testing the project, finding issues, and confirming changes. In addition, I've had less and less time and energy for the work of open source maintenance. I'm sorry that this has impacted this project.My hope with migrating to jazzband is that it would be easier for the users of the project to identify themselves and take over maintenance. I think a clear statement in the project README would help this along.
Here's my first draft:
Note to users:
Nose has been in maintenance mode since at least 2015.
django-nose
is in maintenance mode as well, and the sole maintainer is no longer an active user. See https://jazzband.co to learn howdjango-nose
is maintained and how you can help. New projects should consider using py.test, or unittest with the Django testing framework.The text was updated successfully, but these errors were encountered: