forked from VimPlug/jedi
Remove __future__ usages
This commit is contained in:
@@ -2,7 +2,6 @@
|
||||
This module is here to ensure compatibility of Windows/Linux/MacOS and
|
||||
different Python versions.
|
||||
"""
|
||||
from __future__ import print_function
|
||||
import errno
|
||||
import sys
|
||||
import os
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
from __future__ import print_function
|
||||
import inspect
|
||||
import types
|
||||
import sys
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
from __future__ import print_function
|
||||
import sys
|
||||
import os
|
||||
import re
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
Utilities for end-users.
|
||||
"""
|
||||
|
||||
from __future__ import absolute_import
|
||||
import __main__
|
||||
from collections import namedtuple
|
||||
import logging
|
||||
|
||||
1
sith.py
1
sith.py
@@ -44,7 +44,6 @@ Options:
|
||||
--pudb Launch pudb when error is raised.
|
||||
"""
|
||||
|
||||
from __future__ import print_function, division, unicode_literals
|
||||
from docopt import docopt
|
||||
|
||||
import json
|
||||
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
|
||||
@@ -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()
|
||||
Reference in New Issue
Block a user