let test_unicode be used as a script for profiling
Add "bad codecs" for decoding bad bytes.

Simply by using a statement such as "import ftfy.bad_codecs", you will be able
to decode popular, messy encodings that Python is too dignified to support,
such as 'sloppy-windows-1252' and 'cesu-8'.
Simplify how sloppy codecs are built
allow sloppy codecs to be cached
fix expected output in 'plan_so_far'
Simplify how charmaps are generated
fix outdated docs
add apply_plan, which applies the result of fix_text_and_explain
remove redundancy for a faster regex
Remove extra output that was slowing down tests.

(So *that's* why it was taking longer!)
finish the guess_bytes function
version 3.1.0
put coding line in test_bytes
Update docstrings based on existence of Python 3.3.3
Output correct 'plans' and test them
Clean up, add some missing pieces, document a lot

For the purpose of documentation, and also because it's generally
useful, this adds the `explain_unicode` function, which prints the name
and codepoint of each character in a Unicode string.

It also adds aliases such as 'sloppy-cp1252' for 'sloppy-windows-1252',
and adds the 'sloppy-cp854' codec.
Merge branch 'codecs' of github.com:LuminosoInsight/python-ftfy into codecs

Conflicts:
	tests/test_unicode.py
fix a doctest that broke on Python 3
Add coding lines to fix python2
Fixes to make flake8 mostly happy