put space around equal sign

[jwijffels]

Hello I'm new to ruff. I only knew ruff from this song from the Prodigy https://www.youtube.com/watch?v=eO82VmHn3fo - more this variant from here: https://youtu.be/jZxLgK07RYM?t=3434 if I recall

Nevertheless, I'm looking for a way to configure ruff with a space around the equal sign. I prefer in the below example the formatting shown in the first line and not the second one (I'm coming from R where the first syntax is more common)

How would you do that in Ruff, put that space around the equal sign or make sure Ruff does not overwrite that if I write it like that?

from itertools import repeat
repeat(4, times = 10) 
repeat(4, times=10)

thanks!

[dhruvmanila]

Hello I'm new to ruff. I only knew ruff from this song from the Prodigy youtube.com/watch?v=eO82VmHn3fo - more this variant from here: youtu.be/jZxLgK07RYM?t=3434 if I recall

Welcome to Ruff! That's very interesting

How would you do that in Ruff, put that space around the equal sign or make sure Ruff does not overwrite that if I write it like that?

This isn't possible because that's the recommended style in Python specifically for function calls and function parameters with default values (and without annotations). Refer to https://docs.astral.sh/ruff/rules/unexpected-spaces-around-keyword-parameter-equals/ and specifically the "Why is this bad?" section.

[jwijffels]

Thanks for the links. That's exactly what I found as well.
What would be the configuration in ruff or another linter to avoid using the unexpected-spaces-around-keyword-parameter-equals (E251) and making sure

repeat(4, times = 10) is not put to repeat(4, times=10)

[injust]

The E251 linter rule isn't enabled by default (and it's also in preview). Instead, the formatting of equal signs is being done by the Ruff formatter, not the linter.

As PEP 8 is basically Python law, I don't think Ruff can disable this formatting, nor would (or should IMO) they add a setting to do so.

[jwijffels]

Thanks for the answer. Do I understand this correctly that it is possible to disable ruff replacing the spaces around the equal sign by enabling the preview mode and exclude E251 from the formatter?
If yes, the how to specify this in the ruff toml file?

[injust]

I edited my original comment to clarify: E251 has nothing to do with the formatter.

[dhruvmanila]

Yes, the E251 is a linter rule. The formatter works in a different way, the formatter only exposes a few configuration options which are available under tool.ruff.format through which you can change the behavior of the formatter.

[jwijffels]

I've put this in my ruff.toml but when

exclude = [
    "__init__.py"
]

line-length = 250
indent-width = 4
preview = true

[lint]
preview = true
fixable = ["ALL"]
unfixable = []
extend-ignore = ["E251"]
ignore = ["E251"]

[lint.per-file-ignores]
"rlike/src/text.py" = [
    "E251",    # space around '=' in parameter assignment
]

[format]
preview = true
quote-style = "single"
indent-style = "space"
skip-magic-trailing-comma = false
line-ending = "auto"
docstring-code-format = false

but when running pre-commit run --all-files where .pre-commit-config.yaml I see it did still the replacement

repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v2.4.0
    hooks:
      - id: trailing-whitespace
      - id: end-of-file-fixer
      - id: check-yaml
        args: ["--unsafe"]
      - id: check-added-large-files
  - repo: https://github.com/charliermarsh/ruff-pre-commit
    rev: "v0.5.4" # Sync with pyproject.toml
    hooks:
      - id: ruff
        args: ["--fix"]
      - id: ruff-format

So is is possible with ruff to not apply these removal of spaces around the equal sign? If no, is there another python package which does this?

[injust]

You have configured extend-ignore and ignore under the [lint] section, which does nothing because, once again, the E251 linter rule is currently disabled by default. Your problem is with the formatter, not the linter.

So is is possible with ruff to not apply these removal of spaces around the equal sign?

No.

[jwijffels]

Ok, clear. Thanks for the help and feedback everyone :)