Skip to content

chore: fix some ruff warnings since version upgrade#1

Open
matmut7 wants to merge 3 commits intopeterjdolan:tqdmfrom
matmut7:tqdm
Open

chore: fix some ruff warnings since version upgrade#1
matmut7 wants to merge 3 commits intopeterjdolan:tqdmfrom
matmut7:tqdm

Conversation

@matmut7
Copy link

@matmut7 matmut7 commented Jun 24, 2025

Hi,

I came accross this PR on the beets project and I guess it was blocked because of some Ruff upgrade that created new warnings. I found that these issues were easily fixed with poe lint --fix --unsafe-fixes now that the Ruff versions mixup has been settled.

I'm really interested in this progress output feature to be released. Sadly, the merge conflicts remaining once I fixed the lint issues are difficult for me to handle. Nevertheless, I'd be glad to lend you a hand if needed.

peterjdolan and others added 3 commits April 21, 2025 20:45
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.

To support consistent use and presentation of the progress bars, and to
allow for future modification, we introduce two methods to beets.ui -
beets.ui.iprogress_bar, and beets.ui.changed_unchanged_error_pbars -
which can be used by Beets' core commands and all Beets plugins. Example
usage is provided in the methods' documentation.

Integrating progress bars into the 'import' command required a more
custom implementation than the beets.ui.* commands could support. The
approach taken is certainly open to discussion.

Notably, the Enlighten library does not work as well in Windows
PowerShell as it does in a linux terminal (manually tested in Zsh), so
the progress bars are disabled in Windows environments. Resolving these
issues and enabling them in Windows is left as future work.
@peterjdolan peterjdolan force-pushed the tqdm branch 2 times, most recently from 7ab870e to f42279b Compare July 27, 2025 20:54
@peterjdolan peterjdolan force-pushed the tqdm branch 3 times, most recently from 523c8f1 to 373e372 Compare September 16, 2025 13:30
@peterjdolan peterjdolan force-pushed the tqdm branch 7 times, most recently from 5bd0bb8 to 4360907 Compare September 26, 2025 21:07
@peterjdolan peterjdolan force-pushed the tqdm branch 4 times, most recently from abb896d to 6b163fe Compare October 12, 2025 19:54
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.

2 participants