3.0.0 was supposed to have removed Python 2 support, but didn't actually remove any of the compatibility shims for Python 2.

In fact, with3b13c11 (#860), further shims were added for Python 2 and going so far as to add future as a dependency and check for Python <= 2.3 (whensys.getfilesystemencoding was added). I'm not sure why#860 was merged with those shims, especially since it was failing a test due to switching to Unicode strings in Python 2, but this commit that did so improperly merged requirements.txt as well, readding gitdb and ddt as dependencies when they had been removed withce21f63 (#826), so that setup.py could use requirements.txt. gitdb itself had actually already been removed as a dependency over 2 years before requirements.txt was updated, with2ca7c01 in v2.0.9.
The commit was then reverted withcc664f0, referencing failing Travis CI tests due to future having been added as a dependency in requirements.txt and the Travis CI configuration installing dependencies from test-requirements.txt, rather than requirements.txt and/or setup.py. The changes were then reintroduced with74a0507, adding installation of requirements.txt (despite what the commit summary says) to the Travis CI configuration. It was then again reverted withc9dbaab, referencing the failing Travis CI build for the previous commit due to the same failing test for the PR.
Afterwards, for some reason, the changes were yet again reintroduced withdac619e, the very commit that dropped Python 2 support. This time, future wasn't even added to requirements.txt, so Python 2 would have failed to import the library even if the commit hadn't dropped support for it. The changes were again reverted with913d806 (for the 3rd time) when Python 2 support was brought back after being dropped in a patch version. They were then introduced again (for the 4th time) with2e7e82b and 3.0.0 was subsequently released with the readded dependencies from almost 3 years ago, leading to#908.#908 was closed withca080bb in 3.0.1, only removing gitdb as a dependency, leading to#911.#911 was then merged withdf5c941 and released as 3.0.2, resolving the dependency issues caused by the improper merge, but leaving the pointless and broken compatibility shims that caused this mess in place.

This PR removes those and other compatibility shims for Python 2 and old Python 3 versions:

• Removefrom builtins import str - This was never even in any release that supported Python 2 and no release ever included future as a dependency.
• Remove check for the existence ofsys.getfilesystemencoding - It has existed since Python 2.3 as mentioned earlier.
• Remove and replacecompat._unichr withchr,comapt.bchr withbytes([...]),compat.binary_type withbytes,compat.bytes_chr withbytes((...,)),compat.FileType withio.IOBase,compat.izip withzip,compat.MAXSIZE withsys.maxsize,compat.mviter with.values(),compat.string_types withstr,compat.text_type withstr,compat.unicode withstr,compat.xrange withrange,compat.UnicodeMixin subclass by using__str__ rather than__unicode__
• Removecompat.byte_ord,compat.PY3,compat.range
• Remove surrogateescape error handler for Python 2
• Remove Python 2 checks forcompat.defenc,TestFun.test_tree_entries_from_data_with_failing_name_decode_py3,TestIndex.test_add_utf8P_path
• Remove Python 2 checks inGit.__unpack_args,compat.with_metaclass,Diff.__str__,TestRepo.test_untracked_files,Actor._main_actor
• Remove Python 3 checks inGitConfigParser._read,_octal_repl,run_commit_hook,git.objects.tree,RefLogEntry.__repr__,Repo._get_untracked_files,TestGit.test_call_unpack_args_unicode,TestGit.test_call_unpack_args
• RemoveTestFun.test_tree_entries_from_data_with_failing_name_decode_py2 Python 2 test
• Remove attempt to importConfigParser for Python 2 ingit.config
• Remove Python 2.7 check inTestBase
• Remove check forlogging.NullHandler for Python 2.6 ingit.util
• Remove Python < 3.3 check forPermissionError ingit.cmd

This PR also fixes the formatting of the version specifier in requirements.txt (so as not to be in parentheses as#826 changed it to be withce21f63) and improves setup.py'spython_requires so as to succinctly specify >=3.4.