Use Python 2/3 compatible float values

This is an ugly hack to work around differences in float representation for
tests.
Resync test data files

This is a lesson in why you shouldn't overlay free and non-free data files with
submodules.  See AST#352788.
Bump copyright years
Define basestring for compatibility with Python 2/3
Refactor XML comparison routines for tests
Python 2/3 compatible imports
Python 2/3 compatible map() use
Use bytestrings for direct XML comparisons
Python 2/3 compatible exception handling
[Tr] Use version info from upoints._version
Encode __repr__ as str/unicode for Python 2/3
Set Python 3.3 classifiers
Merge branch 'feat/python2_3'

* feat/python2_3:
  Set Python 3.3 classifiers
  Encode __repr__ as str/unicode for Python 2/3
  [Tr] Use version info from upoints._version
  Python 2/3 compatible exception handling
  Use bytestrings for direct XML comparisons
  Python 2/3 compatible map() use
  Python 2/3 compatible imports
  Refactor XML comparison routines for tests
  Define basestring for compatibility with Python 2/3
  Resync test data files
  Use Python 2/3 compatible float values
Enable Python 3.3 on travis runs
[Tr] Minor typo fix
Use PEP-3101 to support custom formatting types

If format() and PEP-3101 had existed when the __str__ methods were written this
would have been the path from the outset.
Remove Unicode mangling for edist output

It was very brittle, and easily broken.  Now we'll just default to Unicode, and
users with poorly configured systems can set the format option.
Mark the package as deprecated

Kind of a sad day, but it should have happened a long time ago.

That said there are no plans to stop fixing bugs, but the package as a whole is
very low priority(as it has been for years in reality).
Merge branch 'f/pep3101_support'

* f/pep3101_support:
  Remove Unicode mangling for edist output
  Use PEP-3101 to support custom formatting types
Clean up Sphinx configuration