The repository currently has no minimal dependency declaration.
Why this matters
Even for a small project, a simple dependency file makes setup easier for:
a fresh local environment
contributors
future maintenance after a break
reproducible test installs
At the moment the dependency footprint is small, but that is exactly why it is easy to document now.
Fix approach
Add either:
a minimal requirements.txt
or a small pyproject.toml
At minimum, document the PyQt5 dependency clearly.
Status
Still open.
Packaging/documentation task, not a runtime bug.
### Problem
The repository currently has no minimal dependency declaration.
### Why this matters
Even for a small project, a simple dependency file makes setup easier for:
- a fresh local environment
- contributors
- future maintenance after a break
- reproducible test installs
At the moment the dependency footprint is small, but that is exactly why it is easy to document now.
### Fix approach
Add either:
- a minimal `requirements.txt`
- or a small `pyproject.toml`
At minimum, document the PyQt5 dependency clearly.
### Status
Still open.
Packaging/documentation task, not a runtime bug.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The repository currently has no minimal dependency declaration.
Why this matters
Even for a small project, a simple dependency file makes setup easier for:
At the moment the dependency footprint is small, but that is exactly why it is easy to document now.
Fix approach
Add either:
requirements.txtpyproject.tomlAt minimum, document the PyQt5 dependency clearly.
Status
Still open.
Packaging/documentation task, not a runtime bug.
Missing requirements.txt or pyproject.tomlto [Task]: Missing requirements.txt or pyproject.toml