Skip to content

chore(deps): remove redundant Pygments pin from requirements.txt (closes #17)#18

Open
timon0305 wants to merge 2 commits intomasterfrom
chore/remove-pygments-17
Open

chore(deps): remove redundant Pygments pin from requirements.txt (closes #17)#18
timon0305 wants to merge 2 commits intomasterfrom
chore/remove-pygments-17

Conversation

@timon0305
Copy link
Copy Markdown
Collaborator

@timon0305 timon0305 commented May 5, 2026

Problem

requirements.txt line 12 pinned Pygments==2.19.2. Application source has zero pygments references — verified via grep -rin pygments across all .py / .html / .js / .css. The line is residue from a stale pip freeze snapshot.

Change

Drop the explicit pin.

Notable nuance worth flagging for the reviewer: pytest 9.x lists pygments as a transitive Requires: (different from 8.x where it was optional / extras-only). So a fresh pip install -r requirements.txt will still install pygments — via pytest's dep tree, not ours. This is a "drop a redundant explicit version pin" change, not a "remove an installed package" change. The benefit is that future pytest bumps which need a different pygments range no longer fight an unrelated explicit pin in this file.

Test plan

Built a clean venv from this requirements.txt and verified end-to-end:

Check Result
pip install -r requirements.txt succeeds
pygments still installed transitively (via pytest) ✅ — version 2.20.0
pytest tests/ 75 / 75 OK
python app.py + curl / ✅ HTTP 200 on http://127.0.0.1:5000/
Static grep finds zero pygments references in app source

Closes #17.

Summary by CodeRabbit

  • Chores
    • Removed unused dependency from project requirements.

 #17)

Application source has zero `pygments` references — confirmed via
grep across all .py / .html / .js / .css. The explicit
`Pygments==2.19.2` pin is residue from a stale pip-freeze snapshot.

Notable: pytest 9.x lists pygments as a transitive `Requires:`
(unlike pytest 8.x where it was optional/extra), so a fresh
`pip install -r requirements.txt` will still install pygments via
the pytest dep tree. Removing the explicit pin is therefore a
"drop a redundant version pin" change, not a "remove an installed
package" change. The benefit: future pytest bumps that bring a
different pygments range no longer fight an unrelated explicit pin.

Verification (clean venv built from this requirements.txt):
- pip install -r requirements.txt: succeeds; pygments 2.20.0 pulled
  transitively by pytest, as expected.
- pytest tests/ : 75/75 OK (was 75/75 before).
- python app.py + curl /: HTTP 200.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0f3fb02b-13d1-4cc4-a932-9652a86a6881

📥 Commits

Reviewing files that changed from the base of the PR and between ceefe1c and 42f6391.

📒 Files selected for processing (1)
  • requirements.txt
💤 Files with no reviewable changes (1)
  • requirements.txt

📝 Walkthrough

Walkthrough

The Pygments==2.19.2 dependency is removed from requirements.txt. Grep verification in the linked issue confirms no source files import or reference Pygments anywhere, making this a stale transitive dependency left over from a previous pip freeze snapshot.

Changes

Dependency Cleanup

Layer / File(s) Summary
Unused Dependency Removal
requirements.txt
Pygments==2.19.2 line is deleted. Verified unused across all .py, .html, .js, and .css source files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 One less wheel upon the path,
Pygments gone, no aftermath—
A phantom dep, now freed at last,
Lighter installs, our future's cast! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: removing the redundant Pygments dependency pin from requirements.txt, matching the actual changeset.
Linked Issues check ✅ Passed The PR fully addresses issue #17 by removing the Pygments==2.19.2 line as required, with verification that no source files reference pygments and tests pass.
Out of Scope Changes check ✅ Passed The PR contains only the single intended change (Pygments line removal) with no unrelated or out-of-scope modifications to other files or dependencies.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/remove-pygments-17

Comment @coderabbitai help to get the list of available commands and usage tips.

@timon0305 timon0305 self-assigned this May 5, 2026
@timon0305 timon0305 requested a review from clean6378-max-it May 5, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove unused Pygments dependency from requirements.txt

1 participant