Releases: MoeMusic/Moe
Release v2.1.4
Release v2.1.3
Release v2.1.2
Release v2.1.1
Release v2.1.0
Release v2.0.0
I'm not particularly happy about how little time as passed between v1.0.0 and this release and I don't expect this timeframe to be the norm. In a perfect world, I'm releasing at most 1-2 major versions per year of Moe. I justified this timeframe as I still don't think there's many people using Moe and the list of breaking changes I wanted to implement had settled at a good number.
With that said, I recommend reading through the following notes before upgrading.
Breaking Changes
-
Use mediafile dependency over moe_mediafile fork (bcda77d)
Now that our changes have been merged into mediafile, there's no longer a need to use our fork.
You may experience issues if you have both moe_mediafile and mediafile installed together. All users upgrading should explicitly uninstall moe_mediafile by running ``pip uninstall moe_mediafile``.
-
DB sessions are now explicitly passed as arguments (228a017)
This helps clarify exactly which functions require the database to be initialized. Also, it helps avoid any potential future issues with relying entirely on a global/thread-local session factory.
The following functions/hooks are affected by this change:
add.add_item- newsessionparametercli.Hooks.add_command- the sub-command functions are now passed asessionparameterconfig.Hooks.register_sa_event_listeners-sessionparameter removedduplicate.resolve_dup_items- newsessionparameterduplicate.Hooks.resolve_dup_items- newsessionparameterduplicate.resolve_duplicates- newsessionparameterduplicate.get_duplicates- newsessionparameterlibrary.lib_item.Hooks.edit_changed_items- newsessionparameterlibrary.lib_item.Hooks.edit_new_items- newsessionparameterlibrary.lib_item.Hooks.process_removed_items- newsessionparameterlibrary.lib_item.Hooks.process_changed_items- newsessionparameterlibrary.lib_item.Hooks.process_new_items- newsessionparameterquery.query- newsessionparameterremove.remove_item- newsessionparameterutil.cli.query.cli_query- newsessionparameter
config.MoeSessionhas also been replaced withconfig.moe_sessionmaker. Sessions should no longer be created by importingMoeSession, and instead should use a session parameter that is created at the top-level of an application. Refer to theconfig.pydocstring as well ascli.pyfor more information on how to handle sessions now. -
Changed CandidateAlbum attributes (9cc69db)
source_stris now split into two fields:plugin_sourceandsource_id. This is so in the future we can check against theplugin_sourceand apply different handling criteria per plugin e.g. import weight values.sub_header_inforenamed todisambigs. The "sub-header" is specific to the cli, so it was renamed to be more generalized.
-
Replaced
lib_patharg forfmt_item_pathwith optionalparentarg (cc267d5)This is more flexible as it allows specifying the direct parent for albums, extras and tracks instead of just albums.
-
Removed sync plugin (ae0889d)
The original idea of the sync plugin to sync multiple metadata sources with one command has some implementation barriers that were not fully fleshed out. Instead, each plugin should just implement their own sync commands.
-
Removed musicbrainz plugin (d171be0)
Musicbrainz is now a third-party plugin to be consistent with Moe's policy that any external source plugins should not be in the core repository.
If you'd like to continue to use musicbrainz as an import source, you can install the new plugin with
pip install moe_musicbrainz. Also, ensure to enable it in your configuration. You can find more information on the [Thid-Pary Plugins]{.title-ref} documentation page. -
Removed
pluginsub-directory and package (d3d756d)Now, rather than having to import an api function as
moe.plugins.add.add_item, it's justmoe.add.add_item. I felt the extrapluginsimport level was unnecessarily verbose. -
Custom fields now require dictionary access (1df625c)
Custom fields must now be accessed via
item.custom["my_custom_field"]i.e. normal dictionary access.I changed this from normal attribute access as overriding
__getattr__and__setattr__(required for transparent attribute access) had some finicky conflicts with sqlalchemy. Also, it prevented type hinting the custom attribute dictionary as well as integration with data serializers such as pydantic.Overall, the more I used them, the more issues I found, and the more it felt like a hack. I believe the new explicit dictionary access for custom attributes will prove to be more bulletproof. It also explicitly delineates normal and custom attributes which can be useful in some cases.
-
Renamed
album_objreference toalbumin tracks and extras (51ff9a9)track.albumnow refers to the actual album object (renamed fromtrack.album_obj) andtrack.albumartisthas been removed. Similarly,extra.album_objhas been renamed toextra.album.The original idea was that
track.albumwas a string that referred to an album's title, whiletrack.album_objwas the actual album object itself.track.albumandtrack.albumartistwere "mapped" attributes of an album directly exposed in the track API due to convention. However, these mapped attributes are not first-class attributes as far as sqlalchemy is concerned, and thus have additional issues and considerations compared to normal attributes. Ultimately, I decided these mapped attributes are not worth the headache.
Performance Enhancements
- Slightly improved start-up time by importing default plugins (0ffd10a)
Build Changes
- Removed pyyaml dependency (2519817)