removed from 'from __future__ import with_statement' imports, they are not needed anymore (python 2.5 is no longer supported)

jedi/api/__init__.py

@@ -8,8 +8,6 @@ possible.
 
 .. warning:: Please, note that Jedi is **not thread safe**.
 """
-from __future__ import with_statement
-
 import re
 import os
 import warnings

jedi/cache.py

@@ -13,8 +13,6 @@ This module is one of the reasons why |jedi| is not thread-safe. As you can see
 there are global variables, which are holding the cache information. Some of
 these variables are being cleaned after every API usage.
 """
-from __future__ import with_statement
-
 import time
 import os
 import sys

jedi/evaluate/__init__.py

@@ -68,8 +68,6 @@ backtracking algorithm.
 
 .. todo:: nonlocal statement, needed or can be ignored? (py3k)
 """
-from __future__ import with_statement
-
 import sys
 import itertools
 

jedi/evaluate/builtin.py

@@ -21,7 +21,6 @@ possible to access functions like ``list`` and ``int`` directly, the same way
 |jedi| access other functions.
 """
 
-from __future__ import with_statement
 from jedi._compatibility import exec_function, is_py3k
 
 import re

jedi/evaluate/imports.py

@@ -11,8 +11,6 @@ correct implementation is delegated to _compatibility.
 This module also supports import autocompletion, which means to complete
 statements like ``from datetim`` (curser at the end would return ``datetime``).
 """
-from __future__ import with_statement
-
 import os
 import pkgutil
 import sys

jedi/parser/representation.py

@@ -33,8 +33,6 @@ statements in this scope.  Check this out:
 
 See also :attr:`Scope.subscopes` and :attr:`Scope.statements`.
 """
-from __future__ import with_statement
-
 import os
 import re
 from inspect import cleandoc

jedi/refactoring.py

@@ -12,8 +12,6 @@ following functions (sometimes bug-prone):
 - extract variable
 - inline variable
 """
-from __future__ import with_statement
-
 import difflib
 
 from jedi import common