Skip to content

[RFE]: add possibility to report which one extension is reporting exact error or warning #8757

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.

Sign up for GitHub

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

Jump to bottom
Closed
kloczek opened this issue Jun 13, 2021 · 1 comment
Closed

[RFE]: add possibility to report which one extension is reporting exact error or warning #8757

kloczek opened this issue Jun 13, 2021 · 1 comment
Labels
topic: reporting related to terminal output and user-facing messages and errors type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@kloczek
Copy link
Contributor

kloczek commented Jun 13, 2021

In case when some error or warnimg is printed it would be good to have some details about which one pytest extension exact error or warning has been reported.
@kloczek kloczek changed the title [RFE]: add possibility to report by which one extension is reported exact error or warning [RFE]: add possibility to report by which one extension is reporting exact error or warning Jun 13, 2021
@kloczek kloczek changed the title [RFE]: add possibility to report by which one extension is reporting exact error or warning [RFE]: add possibility to report which one extension is reporting exact error or warning Jun 13, 2021
@kloczek kloczek mentioned this issue Jun 13, 2021
Closed
@Zac-HD Zac-HD added topic: reporting related to terminal output and user-facing messages and errors type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature labels Jun 14, 2021
@Zac-HD
Copy link
Member

Zac-HD commented Jul 6, 2024

I think you can get this from python -Werror -m pytest and the traceback?

Closing per #12465 (comment) since I don't think we need to do anything.

@Zac-HD Zac-HD closed this as not planned Won't fix, can't repro, duplicate, stale Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: reporting related to terminal output and user-facing messages and errors type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Zac-HD @kloczek