Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nose is unmaintained and we need to switch [RFC] #773

Closed
diegogangl opened this issue Feb 7, 2022 · 2 comments · Fixed by #792
Closed

Nose is unmaintained and we need to switch [RFC] #773

diegogangl opened this issue Feb 7, 2022 · 2 comments · Fixed by #792
Labels
enhancement maintainability Automated tests suite, tooling, refactoring, or anything that makes it easier for developers priority:high RFC "Request for Comments" brainstorming tickets for things we are unsure about

Comments

@diegogangl
Copy link
Contributor

According to the Nose website:

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.

https://nose.readthedocs.io/en/latest/

Well this has certainly happened, nose doesn't work anymore with Python 3.10. Fedora has already switched to it in 35, so I just got hit by this. Making the tests run with Python 3.9 while 3.10 is the default makes the gi module fail for some reason, so that's also not an option.

The question is whether we should switch to Nose2 (easier?) or move to Pytest (nicer?). Or use something different altogether

@Neui
Copy link
Contributor

Neui commented Feb 7, 2022

I am not really in the python ecosystem, so I don't really have a preference (yet). Pytest has a page about using nose tests which could make it easier to migrate, but looking at nose2 vs nose differences it seems nose2 may just (mostly) work with our existing tests (haven't really dealt with them yet).

I have a small (paused) python project myself, but looking at the test I mainly just use unittest it seems, and I think I just ran whatever setup.py test (or something like that?) does...

@diegogangl
Copy link
Contributor Author

Pytest has a page about using nose tests which could make it easier to migrate

That's a great find! They even have a migration script, might try that out later

@nekohayo nekohayo added RFC "Request for Comments" brainstorming tickets for things we are unsure about maintainability Automated tests suite, tooling, refactoring, or anything that makes it easier for developers labels Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement maintainability Automated tests suite, tooling, refactoring, or anything that makes it easier for developers priority:high RFC "Request for Comments" brainstorming tickets for things we are unsure about
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants