Feature: Add progress bars

[peterjdolan]

Description

Many long-running commands produce little or no feedback in the terminal to indicate that they're progressing, and none of them provide estimates of how long the operation will run. This change introduces the enlighten python package, which displays progress bars akin to TQDM below the existing terminal output.

See tracking issue

To Do

• Documentation. (If you've added a new command-line flag, for example, find the appropriate page under docs/ to describe it.)
• Changelog. (Add an entry to docs/changelog.rst to the bottom of one of the lists near the top of the document.)
• Tests. (Very much encouraged but not strictly required.)

Example screenshots

[github-actions]

Thank you for the PR! The changelog has not been updated, so here is a friendly reminder to check if you need to add an entry.

[peterjdolan]

Import operation partially implemented; still needs some work. Example screenshot above.

[Copilot]

Copilot reviewed 24 out of 25 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• docs/changelog.rst: Language not supported

[Copilot]

Copilot reviewed 24 out of 25 changed files in this pull request and generated no comments.

Files not reviewed (1)

• docs/changelog.rst: Language not supported

Comments suppressed due to low confidence (1)

beetsplug/replaygain.py:1560

• Removal of the SystemExit and KeyboardInterrupt exception handling in the replaygain command may affect how user interruptions are managed. Please confirm that propagating these exceptions, rather than silencing them, is the intended behavior.

finally:

[peterjdolan]

@snejus I'm not sure why the latest push is failing the automatic lint and formatting; it passes 'poetry run poe lint && poetry run poe format' on my machine just fine. Any suggestions? I've already sync'd my fork to beets master and rebased.

[wisp3rwind]

This seems to be related to some combination of (although I'm not seeing the full picture yet)

• you regenerated the lockfile, which now chooses a newer version of ruff
• https://github.com/astral-sh/ruff/blob/6bdffc3cbff2194afdff0e46fccb03cf6147d367/CHANGELOG.md?plain=1#L987
• [flake8-type-checking] Adds implementation for TC006 astral-sh/ruff#14511
• maybe, you're still running another ruff version locally

Someone should probably open a new PR to fix all TC006 warnings, include TC in our ruff rule selection instead of TCH, and probably fix ruff to a major version (a 0.X.*). Since major ruff updates might contain breaking rule/style changes, I'd guess that we'd only want to bump it manually.

I do get the same TC006 error if I locally run the system-installed ruff 0.11.0.