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
Since it's now possible to move the setuptools configuration from setup.cfg into pyproject.toml (#53) if we can also get the pycodestyle configuration out of setup.cfg then we could get rid of the setup.cfg file entirely and have one less root file.
We could remove pycodestyle from our projects. How much value does it really provide given that we have Black, isort and Pylint? There's a list of pycodestyle's warnings here: https://pycodestyle.pycqa.org/en/latest/intro.html#error-codes At a glance it doesn't look like to me like pycodestyle is providing any value. All of the warnings look like things that should never happen to Black- and isort-formatted code apart from a handful of warnings that I think Pylint might already cover anyway
The text was updated successfully, but these errors were encountered:
Since it's now possible to move the
setuptools
configuration fromsetup.cfg
intopyproject.toml
(#53) if we can also get thepycodestyle
configuration out ofsetup.cfg
then we could get rid of thesetup.cfg
file entirely and have one less root file.pycodestyle
doesn't supportpyproject.toml
and it doesn't look like they're going to be adding support any time soon, so for the time being we have two options:pycodestyle
does support reading its configuration fromtox.ini
so we could move thepycodestyle
config fromsetup.cfg
intotox.ini
. See https://pycodestyle.pycqa.org/en/latest/intro.html#configurationpycodestyle
from our projects. How much value does it really provide given that we have Black, isort and Pylint? There's a list ofpycodestyle
's warnings here: https://pycodestyle.pycqa.org/en/latest/intro.html#error-codes At a glance it doesn't look like to me likepycodestyle
is providing any value. All of the warnings look like things that should never happen to Black- and isort-formatted code apart from a handful of warnings that I think Pylint might already cover anywayThe text was updated successfully, but these errors were encountered: