You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our projects setup.cfg we often add --black via addopts, so our CI always runs with black and any other project specific options that may be required:
[tool:pytest]
addopts = -n auto --black
However there are often cases when developing locally you do not wish to have your tests fail due to black. This poses a problem, because you have to edit your setup.cfg to remove --black and remember to add it back again when committing.
It would be really handy to have a --no-black argument that can be given that overrides the --black flag, if present. So a full invocation might expand to pytest --black --no-black, which would not run black.
In our projects
setup.cfgwe often add--blackviaaddopts, so our CI always runs with black and any other project specific options that may be required:However there are often cases when developing locally you do not wish to have your tests fail due to black. This poses a problem, because you have to edit your
setup.cfgto remove--blackand remember to add it back again when committing.It would be really handy to have a
--no-blackargument that can be given that overrides the--blackflag, if present. So a full invocation might expand topytest --black --no-black, which would not run black.