Function is not accessed (although it IS accessed) about pylance-release HOT 3 CLOSED

Pyright (the type checker that underlies pylance) is working as intended here. These symbols are not referenced anywhere in the file. You appear to have enabled the reportUnusedImport diagnostic error, which is off by default. When you enable this check, pyright will report an error if your file includes an imported symbol that is not used anywhere within the module and is not re-exported to other modules. In your case, I suspect you intend for these symbols to be re-exported to other modules. By default, symbols imported into a module are assumed to be private (internal) to that module. If you intend to re-export them to other modules, you need to use one of the techniques documented here. You can either include them in an __all__ or use a redundant form of import (for example, from x import y as y). This convention was established in PEP 484 for stub files, but the typing community has since adopted it for ".py" files as well.

If you don't want pyright to generate an error for unreferenced imports, you can choose to disable the reportUnusedImport in your project or on a per-file basis using a # pyright: reportUnusedImport=false at the top of the file.

from pylance-release.

@erictraut, thank you very much for your answer. Yes, you are right: they are not referenced in the file.
However, this file __init__.py means that this is a package, which later will be used by other modules. In my case, I am writing

from spark_framework import *

from other parts of the code, and due to this import of functions that is surrounded by red rectangle on my screenshot, they are imported fine.

However, it looks like Pylance doesn't recognize it to be in the __init__.py and doesn't get the real intention.

from pylance-release.

However, this file __init__.py means that this is a package, which later will be used by other modules.

As Eric mentioned above, if you want to re-export these symbols from this module (and you want a static type checker to understand that that is your intention) you'll either need to include them in an __all__ or use a redundant import form (from x import y as y).

I've copied that part of his response here:

By default, symbols imported into a module are assumed to be private (internal) to that module. If you intend to re-export them to other modules, you need to use one of the techniques documented here. You can either include them in an __all__ or use a redundant form of import (for example, from x import y as y). This convention was established in PEP 484 for stub files, but the typing community has since adopted it for ".py" files as well.

from pylance-release.