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

Support -r w and remove --disable-warnings argument #5066

Open
blueyed opened this issue Apr 7, 2019 · 3 comments
Open

Support -r w and remove --disable-warnings argument #5066

blueyed opened this issue Apr 7, 2019 · 3 comments
Labels
topic: config related to config handling, argument parsing and config file topic: reporting related to terminal output and user-facing messages and errors type: deprecation feature that will be removed in the future type: enhancement new feature or API change, should be merged into features branch

Comments

@blueyed
Copy link
Contributor

blueyed commented Apr 7, 2019

It was added in e04d9ff by @aostr, and its only purpose is to remove the "w" in reportopts.

In #1668 (comment) it is mentioned that this was discussed with @hpk42.

The main intention here appears to be to enable them by default.

I suggest adding support for -w in reportchars instead.

This would also allow for something like a-s to have everything, without "skipped" easily.

(came here because I want to add A also to also include pP passed ones)

blueyed added a commit to blueyed/pytest that referenced this issue Apr 7, 2019
blueyed added a commit to blueyed/pytest that referenced this issue Apr 7, 2019
@nicoddemus
Copy link
Member

I like to be able to pass -w in front of a report char in order to hide it from the output.

To give some more context, I believe this option was added as a quick way to disable warnings because at that time we have decided to show internal warnings by default, and thought people would get annoyed (and people did). Since then a lot has changed, with us dropping the internal warnings system and showing all warnings by default (and more people got annoyed too hehehe).

But it doesn't seem necessary to actually remove the option, does it? Or is just a matter to cleanup what we believe is mostly an unused option?

@nicoddemus nicoddemus added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label Apr 9, 2019
@blueyed
Copy link
Contributor Author

blueyed commented Apr 11, 2019

But it doesn't seem necessary to actually remove the option, does it? Or is just a matter to cleanup what we believe is mostly an unused option?

Yes, for cleanup.

I like to be able to pass -w in front of a report char in order to hide it from the output.

Cool.

@nicoddemus
Copy link
Member

Yes, for cleanup.

I see, thanks. 👍

I agree, definitely sounds good. We just have to follow the normal deprecation procedure: emit warnings and only remove it effectively in 5.0. 😁

@nicoddemus nicoddemus added the type: deprecation feature that will be removed in the future label Apr 11, 2019
@blueyed blueyed closed this as completed Nov 27, 2019
@blueyed blueyed reopened this Jan 14, 2020
blueyed added a commit to blueyed/pytest that referenced this issue Jan 22, 2020
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
blueyed added a commit to blueyed/pytest that referenced this issue Jan 26, 2020
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
blueyed added a commit to blueyed/pytest that referenced this issue Jan 26, 2020
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
blueyed added a commit to blueyed/pytest that referenced this issue Jan 27, 2020
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
blueyed added a commit to blueyed/pytest that referenced this issue Jan 28, 2020
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
@Zac-HD Zac-HD added topic: reporting related to terminal output and user-facing messages and errors topic: config related to config handling, argument parsing and config file type: enhancement new feature or API change, should be merged into features branch and removed type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature labels Jul 6, 2024
@Zac-HD Zac-HD changed the title Remove --disable-warnings option? Support -r w and remove --disable-warnings argument Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: config related to config handling, argument parsing and config file topic: reporting related to terminal output and user-facing messages and errors type: deprecation feature that will be removed in the future type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Development

No branches or pull requests

3 participants