Demo Lint Error Resolution

This guide shows a quick, practical workflow to find and resolve common Python linting errors using pylint and flake8. Follow the steps below to set up linting, interpret typical messages, and apply fixes that improve code quality and PEP 8 compliance.

A presentation slide titled "Lint Error Resolution" with a large dark-blue curved shape on the right containing the word "Demo" in bright blue. The bottom-left shows "© Copyright KodeKloud."

Prerequisites

Install the common Python linters:

pip install flake8 pylint

You should see installation output similar to:

Successfully installed flake8-7.1.2 pylint-3.3.6 pyflakes-3.2.0 pycodestyle-2.12.1 ...

Create a baseline `.pylintrc`

Add a .pylintrc to your repository to enforce consistent rules across local development and CI. Example configuration:

jobs=1
load-plugins=
extension-pkg-whitelist=

[MESSAGES CONTROL]
disable=C0114,C0115,C0116

[REPORTS]
output-format=colorized
reports=no
score=yes

[FORMAT]
max-line-length=79
indent-string='    '
indent-after-paren=4
expected-line-ending-format=LF

[DESIGN]
max-args=5
max-locals=15

This configuration disables missing-docstring checks at the top level (so you can add them gradually) and enforces formatting preferences close to PEP 8.

Run pylint

Run pylint against a module:

pylint app.py

Typical pylint output lists issues (trailing whitespace, missing docstrings, line-too-long, import order, etc.). Example excerpt:

************* Module app
app.py:144:0: C0303: Trailing whitespace (trailing-whitespace)
app.py:194:0: C0301: Line too long (105/100) (line-too-long)
app.py:227:0: C0304: Final newline missing (missing-final-newline)
app.py:1:0: C0114: Missing module docstring (missing-module-docstring)
app.py:16:9: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
app.py:37:13: W0613: Unused argument 'e' (unused-argument)
app.py:203:16: W0622: Redefining built-in 'id' (redefined-builtin)
app.py:5:0: C0411: standard import "datetime.datetime" should be placed before third party import "flask.Flask" (wrong-import-order)
---------------------------------------------------------------------------
Your code has been rated at 7.11/10

Common issues and how to address them

The table below maps frequent pylint/flake8 messages to causes and quick fixes.

Issue	Cause	Fix
Trailing whitespace	Extra spaces/tabs at end of lines	Trim trailing whitespace; enable editor trim-on-save
Missing final newline	File does not end with a newline	Add one blank line at end of file
Missing module/function docstrings	No docstring present	Add concise module/function docstrings
Using open() without encoding	open() defaults to system encoding	Use `encoding='utf-8'` (e.g., `open(..., encoding='utf-8')`)
Redefining builtin (e.g., `id`)	Parameter or variable shadows a builtin	Rename to `task_id`, `item_id`, etc.
Wrong import order	Imports not grouped properly	Order: standard library, third-party, local; remove unused imports

Example: cleaned route and query snippet

Here is an excerpt of a Flask route with an SQL query (trailing whitespace removed and formatted):

def login():
    return render_template('login.html')

@app.route('/logout')
def logout():
    session.clear()
    return redirect(url_for('login'))

@app.route('/dashboard')
@login_required
def dashboard():
    db = get_db()
    status_filter = request.args.get('status', '')
    user_filter = request.args.get('user', '')

    query = '''
SELECT t.id, t.title, t.description, t.status, t.created_at,
       creator.username as created_by, assignee.username as assigned_to
FROM tasks t
JOIN users creator ON t.created_by = creator.id
JOIN users assignee ON t.assigned_to = assignee.id
WHERE 1=1
'''

    params = []
    if status_filter:
        # build params and extend query as needed
        pass

Fixing specific issues — before & after examples

Final newline missing

Add an empty line at the end of the file and re-run pylint.

Missing function docstring

Before:

def some_handler(e):
    # handler body...
    pass

After:

def some_handler(e):
    """Handle the incoming error event and return an appropriate response."""
    # handler body...
    pass

Unspecified encoding when using open()

Before:

def read_csv(file_path):
    with open(file_path, 'r') as f:
        csvreader = csv.reader(f)
        for row in csvreader:
            print(row)

After:

import csv
import os

def read_csv(file_path):
    """Read and print rows from a CSV file using UTF-8 encoding."""
    with open(file_path, 'r', encoding='utf-8') as f:
        csvreader = csv.reader(f)
        for row in csvreader:
            print(row)

Redefining builtin id

Before:

def get_task(id):
    # do something with id
    pass

After:

def get_task(task_id):
    """Return task data for the given task_id."""
    # use task_id throughout the function
    pass

Import order and unused imports

Fix by grouping and removing unused imports:

# Standard library imports
import os
import csv
from datetime import datetime
import hashlib
import logging

# Third-party imports
from flask import Flask, render_template, request, redirect, url_for, flash, session, g

# Initialize Flask app
app = Flask(__name__)
app.config['SECRET_KEY'] = 'dev'  # Change this to a random secret key in production
app.config['DATABASE'] = os.path.join(app.instance_path, 'task_manager.sqlite')

Re-run pylint and track improvements

After applying fixes, re-run pylint. You should see many messages disappear and your score improve. Example:

Your code has been rated at 7.33/10 (previous run: 7.11/10, +0.22)

Using editor or assistant helpers

Many editor-integrated assistants or IDE linters can parse pylint output and offer quick fixes (trim whitespace, add final newline, add simple docstrings, rename variables). Use these tools to speed up the cleanup, but always verify the changes.

Keep a .pylintrc (or similar) in your repository so CI, local dev, and any code generators (Cursor AI rules) produce consistent, PEP 8–aligned code. Run linters locally and in CI to catch regressions early.

When using automated assistants, confirm the file path before applying changes. Some tools may duplicate files (e.g., create both app.py and kodekloudtaskmanager.py) or apply edits to the wrong target—delete duplicates and reapply fixes if necessary.

Summary & recommended workflow

Install flake8 and pylint and add a .pylintrc for consistent rules.
Run pylint app.py, inspect messages, and apply fixes for:
- trailing whitespace
- missing final newline
- missing docstrings
- encoding on file open
- import order and unused imports
- builtin name shadowing
Use editor/assistant helpers to speed fixes but verify file paths and changes to avoid duplicates.
Store lint configuration in your repo and run linters in CI to prevent regressions.

Introduction to Cursor

Mastering Autocompletion

Interacting with your Codebase

Inline Editing and Debugging

Terminal Productivity

Understanding and Customizing Cursor

Demo Lint Error Resolution

Prerequisites

Create a baseline `.pylintrc`

Run pylint

Common issues and how to address them

Example: cleaned route and query snippet

Fixing specific issues — before & after examples

Re-run pylint and track improvements

Using editor or assistant helpers

Summary & recommended workflow

Watch Video

​Prerequisites

​Create a baseline .pylintrc

​Run pylint

​Common issues and how to address them

​Example: cleaned route and query snippet

​Fixing specific issues — before & after examples

​Re-run pylint and track improvements

​Using editor or assistant helpers

​Summary & recommended workflow

Watch Video

Prerequisites

Create a baseline `.pylintrc`

Run pylint

Common issues and how to address them

Example: cleaned route and query snippet

Fixing specific issues — before & after examples

Re-run pylint and track improvements

Using editor or assistant helpers

Summary & recommended workflow