- output path no longer has fallbacks
- refactor accuraterip cache
- use requests to download accuraterip entries
- add tests for accuraterip functionality
- remove gobject support from accuraterip-checksum calculation
- default track template now includes extension
- begin to remove support for continuing rip
- begin to use print instead of sys.stdout.write() throughout
* Use cdrdao to detect CD-Rs and continue ripping only if the argument --cdr is passed.
* Get and display disc format from MusicBrainz.
* Add info about CD-R detection to logger
* Remove Musicbrainz medium format info
* add cdrdao command to logger
* Fix for PEP8
* Fix line break
os.path.split() only even splits into two components, which means that
path templates that have more than two parts (e.g., `%A/%d - %y/%X`)
will not get split properly for the purpose of added disambiguation
parts to them.
os.path.join() will still work fine to splice the split template back
together as it takes an arbitrary number of arguments.
Some of these might not occur in the wild, but we theoretically support
them at least, and making sure they work might catch other issues we
didn't think of yet.
Commit b6fb7e8a86 fixes all current flake8
errors, so unsetting this `allow_failures` makes sure that any PEP8 or
similar syntax mistakes get caught immediately.
I left the "THOMAS" part in for now, but this seems more like a debug
message than a user facing message to me—but it was also obviously
something @thomasvs left in for himself, so maybe the whole if clause
has no reason to still be there and should just get removed.
Some of this seems to be debug code which has been left in, some of it
seems to just be old code that was commented out and never put back in
and probably just forgotten about. Either way, we use git for a reason,
so there's no need for these code snippets to stick around. The code
history can be inspected and old code retrieved that way.
Make MusicBrainz consistently written as "MusicBrainz" and not
"musicbrainz" or "Musicbrainz".
Doesn't change instances that refer to the Python module or similar.
A script that sets up an environment for running whipper without
actually installing it. With the clean ups that have happened to whipper
as well as later developments in the Python eco system, simply setting
up a virtualenv and running whipper from within that seems like a more
reasonable approach at this time.
This also fixes https://github.com/JoeLametta/whipper/issues/47 by
removing the "morituri-uninstalled mode" completely. :)
Not actually used by anything in the current codebase and PyChecker
doesn't seem to be the recommended Python code style checker or linting
tool currently. If we need a configuration file for another tool later
on, we can make one then based on current need and wants.
Was added in 2009 and not updated since. There are several Python
coverage tools out there, and the current ./COVERAGE doesn't seem to be
generated using this script either.
pep8.py was added in 2012. Since then, we now have flake8 and a number
of other really good PEP 8 (and other style, best practice, etc.) code
checkers/linters. It doesn't make sense to track this directly in the
repository. If we want to do automated code style/sanity checking, we
should add a dependency on an actually maintained program/script rather
than keeping it locally in the repository.