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 my company we have lots of microservices and nanoservices, and a Python project prototype I maintain to guide how Python projects must be developed and updated.
It's a common complaint not to have default rules in our pyproject.toml files, and instead have "magic letters" just because "I chose them".
My job is to ensure data engineers develop software as we do in .NET, i.e. with types.
I want to propose a group of default linter rules, and choose them with groups (letters), instead of choosing a subset.
We're going to recategorize all of the rules (roughly discussed in #1774) and define new defaults eventually. We're actively working on this, but I'm not sure when we'll be done because it's a big project and we want to get it right.
In my company we have lots of microservices and nanoservices, and a Python project prototype I maintain to guide how Python projects must be developed and updated.
It's a common complaint not to have default rules in our
pyproject.toml
files, and instead have "magic letters" just because "I chose them".My job is to ensure data engineers develop software as we do in .NET, i.e. with types.
I want to propose a group of default linter rules, and choose them with groups (letters), instead of choosing a subset.
pyproject.toml
Reasoning of
select
:==
, etc.Reasoning of
ignore
:self
andcls
is strange in Python.Any
.Besides, I always use this configuration:
The text was updated successfully, but these errors were encountered: