Skip to content

Conversation

@tarcisiofischer
Copy link
Contributor

closes #8337

I was in doubt if this change needs a changelog, and, if it needs, if I should add trivial or docs (because it is both, IMO)

Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

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

Thanks @tarcisiofischer!

Small suggestion on the changelog, other than that LGTM!

@tarcisiofischer
Copy link
Contributor Author

Is there any way I can see the generated docs before merging? I didn't check the produced HTML file 🤔

@nicoddemus
Copy link
Member

Is there any way I can see the generated docs before merging? I didn't check the produced HTML file 🤔

There's a readthedocs build that you can see the generated HTML:

https://pytest--8615.org.readthedocs.build/en/8615/

image

@tarcisiofischer
Copy link
Contributor Author

LGTM. Ready to merge.

@nicoddemus
Copy link
Member

FYI I've fixed the changelog and moved the suggestion to a "Note" box at the end of the text, which I believe it is better. 👍

@nicoddemus nicoddemus requested a review from Zac-HD May 4, 2021 10:57
@nicoddemus
Copy link
Member

Note: we should squash this IMHO.

Co-authored-by: Zac Hatfield-Dodds <[email protected]>
@nicoddemus nicoddemus requested a review from Zac-HD May 4, 2021 23:54
@nicoddemus nicoddemus merged commit b7416f7 into pytest-dev:main May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Recommend np.testing module instead of pytest.approx with Numpy arrays

3 participants