Remove __future__ usages

test/examples/absolute_import/local_module.py

@@ -1,14 +0,0 @@
-"""
-This is a module that imports the *standard library* unittest,
-despite there being a local "unittest" module. It specifies that it
-wants the stdlib one with the ``absolute_import`` __future__ import.
-
-The twisted equivalent of this module is ``twisted.trial._synctest``.
-"""
-from __future__ import absolute_import
-
-import unittest
-
-
-class Assertions(unittest.TestCase):
-    pass

test/examples/absolute_import/unittest.py

@@ -1,14 +0,0 @@
-"""
-This is a module that shadows a builtin (intentionally).
-
-It imports a local module, which in turn imports stdlib unittest (the
-name shadowed by this module). If that is properly resolved, there's
-no problem. However, if jedi doesn't understand absolute_imports, it
-will get this module again, causing infinite recursion.
-"""
-from local_module import Assertions
-
-
-class TestCase(Assertions):
-    def test(self):
-        self.assertT

test/refactor.py

@@ -4,7 +4,6 @@ Refactoring tests work a little bit similar to integration tests. But the idea
 is here to compare two versions of code. If you want to add a new test case,
 just look at the existing ones in the ``test/refactor`` folder and copy them.
 """
-from __future__ import with_statement
 import os
 import platform
 import re

test/test_inference/test_absolute_import.py

@@ -1,12 +0,0 @@
-"""
-Tests ``from __future__ import absolute_import`` (only important for
-Python 2.X)
-"""
-from jedi import Project
-from .. import helpers
-
-
-def test_can_complete_when_shadowing(Script):
-    path = helpers.get_example_dir('absolute_import', 'unittest.py')
-    script = Script(path=path, project=Project(helpers.get_example_dir('absolute_import')))
-    assert script.complete()