PyCQA / PyCQA/pycodestyle

E128: Indentation checks could contain exact information

Open
#928 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5.2k
Forks
754
PR merge metrics
No merged PRs in 30d

Description

It could be more helpful for a developer new to a codebase, that perhaps doesn't know the indentation still in use, to be told exactly where the indentation should go.

This could just be added to the end of the error like (expected 20, got 8).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This repository is a single Python file; start by locating the E128 indentation check and its diagnostic formatting. Update the message to include the expected and actual indentation values, then run the existing test suite and confirm E128 reports the exact values without breaking current checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.