Py3 changes, Py2 backwards compatibility fix

Rationale: Target current Python release and provide *backwards* compatibility if needed. Don't target legacy releases.
Tested (in app) with Python 3.4 and loaded with Python 2.7.
Updated setuptools classifiers

I have no tox at hand so my integration "tests" should be validated properly for all Python releases (2.7, 3.2, 3.3, 3.4?). `2to3` only really complained the import of Queue so I changed only that but you may want to validate all other issues as well.
Py3 exception logging, issue #17

Previous commit didn't verify logging of exceptions.

Critical issues:
- types.TypeType is now built-in, added legacy switch
- filter yields `TypeError: 'filter' object is not subscriptable`,
changed to list comprehension (since it was used already the previous
line)

2to3 also complained the use of map over list comprehension, changed for
similar rationale.
Revert "Py3 exception logging, issue #17"

This reverts commit ef6dd5875e37ebec13a8a7fa06f849161b35b2bf.
Py3 exception logging, issue #17

Previous commit didn't verify logging of exceptions.

Critical issues:
- types.TypeType is now built-in, added legacy switch
- filter yields `TypeError: 'filter' object is not subscriptable`,
changed to list comprehension (since it was used already the previous
line)

2to3 also complained the use of map over list comprehension, changed for
similar rationale.
Merge pull request #19 from lusitania/py3py2

Py3 compatibility as proposed in issue #17