* the list of contributors is now in a separate file, `AUTHORS`. Why? Because this is meta-information which applies to the entire project, not just one particular module. Also, this file can and should be extended to indicate the authors' different roles (owner, maintainer, contributor, etc). Many successful projects follow this layout, e.g. [django](https://github.com/django/django/blob/master/AUTHORS) and [Swift](https://github.com/openstack/swift). We should adopt it as well.
* Argument parsing has been extracted to `configuration.py` and the names have been changed to follow PEP-8. Unnecessarily complicated boolean conditions have been simplified
* unused imports have been removed
## TESTING
I did my best not to introduce any bugs in the process, but it doesn't seem we have any tests at all for the command-line interface and option parsing, so this will require thorough review! I'm looking forward to any comments and improvements, and please let me know if I broke `devscripts/bash-completion.py` or not.
GitHub [recognizes this file](https://github.com/blog/1184-contributing-guidelines) and displays a prominent, yellow-highlighted link to it for everyone who is trying to report a bug or submit a pull-request, making it much for likely that contributors will find this information. This should help cut down on duplicate and incomplete bug reports.
Of course, README links to the new file. (GitHub now [supports relative links](https://github.com/blog/1395-relative-links-in-markup-files) in markdown].)
So I checked for usages of this class, and it turns out the only place it is used is in `youtube_dl/__init__.py`.
Actually, the only method used is `FileDownloader.parse_bytes`, which is defined as a static method in `.downloader/FileDownloader` anyway!
The old `FileDownloader._do_download` is never used.
To summarize, the class can safely be deleted (unless my IDE and I missed something).
