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
I was halfway through writing this when I saw that #3896 did a very similar thing after 3.7 support was dropped in #3765.
It is not a coincidence that every file changed in that PR also needs changing again for dropping 3.8 support, along with at least a couple others. It would be pretty cool if updates to documentation, error messages, etc. could be more of a standard part of changes like this in the future. Tests also may need updating. Thanks!
The text was updated successfully, but these errors were encountered:
The latest version (24.10.0) drops Python 3.8 runtime support via #4452. Error messages and documentation were not updated outside of the changelog.
This creates significant conflicting information between actual requirements and installation instructions, error messages, etc.
Here are a few places (not an exhaustive list) that need updating:
README.md
black/README.md
Lines 39 to 42 in 1b2427a
getting_started.md
black/docs/getting_started.md
Lines 17 to 20 in 1b2427a
docs/faq.md
black/docs/faq.md
Lines 85 to 96 in 1b2427a
docs/integrations/editors.md
black/docs/integrations/editors.md
Lines 237 to 241 in 1b2427a
autoload/black.vim
black/autoload/black.vim
Lines 77 to 80 in 1b2427a
plugin/black.vim
black/plugin/black.vim
Lines 22 to 30 in 1b2427a
tox.ini might need updating but I'm not certain:
black/tox.ini
Line 3 in 3dcacdd
I was halfway through writing this when I saw that #3896 did a very similar thing after 3.7 support was dropped in #3765.
It is not a coincidence that every file changed in that PR also needs changing again for dropping 3.8 support, along with at least a couple others. It would be pretty cool if updates to documentation, error messages, etc. could be more of a standard part of changes like this in the future. Tests also may need updating. Thanks!
The text was updated successfully, but these errors were encountered: