Porting code to be compatible with py3 and py2

Hey, folks!

I ported the code to work also for Python 3 (specifically, 3.3 and 3.4).

Summary of the changes:

* using absolute imports instead of relative
* adjusted tox.ini and .travis.yml to test also with py3
* adapted new_relativedelta overriding ``__init__`` instead of ``__new__``
* using dict.items and dict.values instead of dict.iteritems and dict.itervalues
* using ``next(some_iter)`` instead of ``some_iter.next()``
* protected code dependant on specific versions (ideally, this would go away)

I'm also commenting below some stuff I'm not sure if it's handled the best way.

@csalazar @Allactaga Any concerns?
I think we should expect the input as unicode, and we shouldn't manage encodings neither in `DateParser` nor in `date.DataDateParser` if possible. Users should pass unicode strings to library. The library shouldn't dictate how will the values be decoded - users should handle that themselves because only users know where the data came from and how should it be decoded.