This release includes the Beta version of the Ruff formatter — an extremely fast, Black-compatible Python formatter.
Try it today with ruff format.
Changes
Preview features
[pylint] Implement non-...
I have a question for all of you fine folks here. I use a library (aws-cdk-lib) that has objects that take many many keyword arguments. We usually put each argument on its own line. I’ve found that these are much easier to read with spaces around the equal sign. But I’ve never seen this mentioned anywhere when looking at formatters. Is this just me? Or is this something that some formatters support?
Don’t use spaces around the = sign when used to indicate a keyword argument, or when used to indicate a default value for an unannotated function parameter
I have a question for all of you fine folks here. I use a library (aws-cdk-lib) that has objects that take many many keyword arguments. We usually put each argument on its own line. I’ve found that these are much easier to read with spaces around the equal sign. But I’ve never seen this mentioned anywhere when looking at formatters. Is this just me? Or is this something that some formatters support?
Never seen it in ten years but it actually does sound more readable
I agree and haven’t found a formatter to do it for me.
It’s against PEP8