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
The verbose would claim that the filesystem root was identified as the project root (this is correct) and the configuration file came from /pyproject.toml (this is false).
To Reproduce
Create a test file in a directory where is no pyproject.toml present (up the filesystem root)
Reformat using the same command and observe the wrong output
❯ black test.py --check -vIdentified `/` as project root containing a file system root.Sources to be formatted: "home/ichard26/programming/oss/test.py"test.py already well formatted, good job.All done! ✨ 🍰 ✨1 file would be left unchanged.
❯ echo"[tool.black] line-length = 10" > ~/.config/black
❯ black test.py --check -vIdentified `/` as project root containing a file system root.Sources to be formatted: "home/ichard26/programming/oss/test.py"Using configuration from project root.would reformat test.pyOh no! 💥 💔 💥1 file would be reformatted.
Expected behavior
That the output would report either it came from user level configuration or at least not claim it was project configuration 'cause it's not.
Describe the bug
The verbose would claim that the filesystem root was identified as the project root (this is correct) and the configuration file came from
/pyproject.toml
(this is false).To Reproduce
--verbose
Expected behavior
That the output would report either it came from user level configuration or at least not claim it was project configuration 'cause it's not.
Environment
Additional context
This made it very confusing to debug an unrelated test suite issue :)
cc @Shivansh-007
The text was updated successfully, but these errors were encountered: