-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add small section on migrating from nose to pytest. #8048
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
Conversation
I don't think it is necessary; I believe only sweeping changes to the documentation are useful to be added to the CHANGELOG. 👍
Yes by all means. 😁 |
nicoddemus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor adjustments. 👍
Thanks!
|
I've included your suggestions and added my name to AUTHORS by force pushing to my |
Hmmm seems like your fork might have been out of date? The builds seem broken... |
|
(Let me know if you want me to rebase/force-push for you) |
|
Yes please |
|
Is there a way I can re-trigger the failed steps? |
The section currently features the nose2pytest tool with plans to expand on some of the common gotchas when performing such migrations.
Unfortunately not, only maintainers can re-trigger (except for pushing a new commit of course). |
|
Thanks @mickeypash! |
Follow-up to pytest-dev#8048 which seems to have been merged without the suggested changes.
This change was initiated after a discussion found here.
The section currently features the
nose2pytesttool with plans to expandon some of the common gotchas when performing such migrations.
Questions for reviewers: