37from harbor_client.models.configurations_response_scan_all_policy import (
38 ConfigurationsResponseScanAllPolicy,
39)
40from harbor_client.models.configurations_response_scan_all_policy_parameter import ( 41 ConfigurationsResponseScanAllPolicyParameter,
42)
43from harbor_client.models.endpoint import Endpoint
81from harbor_client.models.configurations_response_scan_all_policy import (
82 ConfigurationsResponseScanAllPolicy,
83)
84from harbor_client.models.configurations_response_scan_all_policy_parameter import ( 85 ConfigurationsResponseScanAllPolicyParameter,
86)
87from harbor_client.models.endpoint import Endpoint
15
16import unittest
17
18import harbor_client19from harbor_client.models.worker_pool import WorkerPool # noqa: E501
20from harbor_client.rest import ApiException
21
16import unittest
17
18import harbor_client
19from harbor_client.models.worker_pool import WorkerPool # noqa: E50120from harbor_client.rest import ApiException
21
22
17
18import harbor_client
19from harbor_client.models.worker_pool import WorkerPool # noqa: E501
20from harbor_client.rest import ApiException21
22
23class TestWorkerPool(unittest.TestCase):
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__
.