3import html
4import traceback
5import base64
6import json 7from jadi import service
8
9from aj.api.http import BaseHttpHandler, HttpPlugin
4import subprocess
5
6from aj.api.http import get, post, delete, HttpPlugin
7from aj.auth import authorize 8from aj.api.endpoint import endpoint, EndpointError
9
10
3from jadi import component
4import subprocess
5
6from aj.api.http import get, post, delete, HttpPlugin 7from aj.auth import authorize
8from aj.api.endpoint import endpoint, EndpointError
9
4from aj.api.http import get, put, post, delete, HttpPlugin
5from aj.auth import authorize
6from aj.plugins.dns_api.record import Record
7from aj.api.endpoint import endpoint, EndpointError 8from aj.plugins.dns_api.manager import DomainManager
9
10
2import logging
3import subprocess
4import os
5import pwd 6from jadi import component
7
8import aj
An object has been imported but is not used anywhere in the file. It should either be used or the import should be removed.
import os
def example():
print("This snippet is not using the `os` import anywhere.")
def example():
print("This looks good now!")
One major reason why this issue can cause confusion is when it's raised for imports that are meant to be exported, for use in other places.
For example, consider this file, mypackage/__init__.py
:
from mypackage.foo import is_foo
from mypackage.bar import bar_function
This is a very common pattern to export common functionality from modules, to
the top level of a package. But there is a major problem with this approach.
Consider this file, mypackage/foo.py
:
import os
def is_foo(item):
return os.path.exists(item)
Since os
is imported inside foo.py
, you can actually do this:
>>> from mypackage.foo import os
Although weird, Python automatically exports all imports in a file. In practice however, it is ill-advised to rely on this behaviour.
If you want to explicitly export an imported item in a file, add it to the
special variable named __all__
:
from mypackage.foo import is_foo
from mypackage.bar import bar_function
__all__ = ['is_foo', 'bar_function'] # Notice that these are strings!
DeepSource won't raise an issue if the imported item is present in __all__
.