beets-alternatives icon indicating copy to clipboard operation
beets-alternatives copied to clipboard

Replace deprecated imports of beets submodules by the new standalone packages

Open wisp3rwind opened this issue 4 years ago • 4 comments

The relevant changes in beets will actually only land in beets>1.4.9. Thus, if and when we merge this, the version requirement for beets also needs to be bumped.

wisp3rwind avatar Oct 31 '20 10:10 wisp3rwind

Makes sense. We should probably add mediafile and confuse as explicit dependencies.

Do we need to? These are integral parts of beets itself, there's no way these can be missing.

We should also make this a major version change (i.e. to 0.11) if we require beets v1.4.9.

Yes, bumping our major version in that case sounds sensible.

We don't really require beets >1.4.9, though. Only the tests depend on the import location, none of the modules has changed, though. So maybe, I should change this PR to check beets' version and do conditional imports. I dislike that idea, but it might be warranted. OTOH, there's probably no good reason for anyone not to upgrade to beets 1.5.0 once it's released. Do you have a clearer preference on how to handle this.

wisp3rwind avatar Nov 02 '20 08:11 wisp3rwind

I totally missed that we only require these for dependencies :facepalm:. We can make mediafile and confuse explicit test dependencies with test_requires. Then the tests with beets 1.4.7 should pass. If this does not work, then I’m ok with bumping the requirement to 1.4.9.

geigerzaehler avatar Nov 02 '20 08:11 geigerzaehler

For what it's worth, I think most beets users at this point just run some rev of master as the releases rarely if ever happen. It would be nice to have this merged and just direct users who want to remain on 1.4.9 to the last release.

lovesegfault avatar Apr 19 '21 05:04 lovesegfault

For what it's worth, I think most beets users at this point just run some rev of master as the releases rarely if ever happen. It would be nice to have this merged and just direct users who want to remain on 1.4.9 to the last release.

I tend to disagree: IIRC, this only leads to warnings when running the tests, and is not otherwise causing any issues, so we may as well postpone merging a bit longer. Or is there any actual situation where these warnings are a problem?

wisp3rwind avatar Apr 19 '21 06:04 wisp3rwind

This should certainly be merged with the updated version requirement in #70.

wisp3rwind avatar Apr 30 '23 09:04 wisp3rwind

This should certainly be merged with the updated version requirement in #70.

@wisp3rwind Would you like to update this PR and I’ll give it another look?

geigerzaehler avatar May 23 '23 06:05 geigerzaehler