Adrian Sampson fe892cc268 attempt at managing album info table in Python instead of with triggers ... I think this is the end of the road for the design that treats albums as a lightweight hanger-on to items. That is, we attempted to keep the interface strictly item-focused; album information was created and deleted on the fly in response to creation and deletion of items. I now believe that this was ultimately a bad idea and can only lead to unexpected behavior and complex implementation. It's time to start over.		2010-07-14 11:55:19 -07:00
..
rsrc	configurable album art path construction	2010-07-13 22:00:42 -07:00
__init__.py	misc. overdue code cleanup	2010-07-09 18:07:15 -07:00
test_art.py	clean up code for art fetcher; add unit tests	2010-07-12 17:49:23 -07:00
test_autotag.py	couple of outdated tests: mock Items didn't have MB fields	2010-07-11 18:19:27 -07:00
test_db.py	attempt at managing album info table in Python instead of with triggers	2010-07-14 11:55:19 -07:00
test_files.py	attempt at managing album info table in Python instead of with triggers	2010-07-14 11:55:19 -07:00
test_mb.py	identify albums by existing MB album ID	2010-07-10 20:10:34 -07:00
test_mediafile.py	detect unreadable files that seem to be of the correct type	2010-07-03 23:44:28 -07:00
test_mediafile_basic.py	MediaFile support for MusicBrainz track, album, and artist IDs	2010-07-10 14:05:01 -07:00
test_player.py	remove outdated references to beets.player module	2010-07-09 18:12:18 -07:00
test_query.py	add MusicBrainz ID fields to database schema	2010-07-10 17:53:51 -07:00
test_ui.py	clean up code for art fetcher; add unit tests	2010-07-12 17:49:23 -07:00
testall.py	make test suite runnable with "setup.py test"	2010-07-08 11:07:56 -07:00