-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove mention of python-itunes #2540
Conversation
The plugin is inactive and has been broken for months: beetbox#2371 Fixes beetbox#1610
@owcz, thanks for your PR! By analyzing the history of the files in this pull request, we identified @sampsyo, @lcharlick and @Lemutar to be potential reviewers. |
Good call; thanks. Would you mind adding a changelog entry to this effect? |
Is keeping the iTunes Store section necessary ?
|
Yep, good point—we can probably remove that section altogether. (Beyond that, this is totally ready to merge—anybody with commit access should feel free to close it up.) Thanks again! |
I recommend keeping the section (or at least a mention) because otherwise users (like me) will wonder where fetchart's iTunes support is. iTunes' artwork is some of the most reliable on the Internet—hopefully someone will fill in this functionality soon |
Gotcha, yet I think it's pretty clear in the first sentence that iTunes artwork is not available :
Have no strong opinion though and the commit to revert is |
As far as I can tell, as currently merged, https://github.com/beetbox/beets/blob/master/docs/plugins/fetchart.rst doesn't include that sentence or any other mention of iTunes |
It's the first sentence of that section : |
Right, but not with "iTunes"—the point is that "iTunes" isn't mentioned at all on the page so, as written, someone looking for iTunes |
Thanks for editing the docs, @owcz, and for merging, @Kraymer. Our usual MO in these situations is to advertise the change loudly and clearly in the changelog instead of in the documentation pages themselves. There's of course a trade-off, but keeping the core documentation changes free of historical cruft has been helpful in making them clear for new users, who just want to see what's currently there. I think our announcement in the changelog could still be louder and clearer, but we'll get there. |
@owcz in the meantime, if iTunes fetchart support is something you want back, you could open a dedicated feature request issue that would bring visibility |
The package is inactive and has been broken for months: #2371
Fixes #1610
Alternatively, could be rephrased to say it doesn't work with py3 (if that's the only condition), but I think that would cause even more confusion if there isn't a workaround