When trying findpydeps -i . throws remove_local_imports not defined error

In my last issue, I noted that I just tried out findpydeps on one of my work repos, using a command line like this:

findpydeps -i . --blocks --functions --follow-local-imports --removal-policy 0 --strict --no-header > ./requirements_from_findpydeps.txt

I think that I understand exactly what these options do:
--blocks --functions
they tell findpydeps to include imports that are locally defined inside blocks and functions (in addition to always including imports at the start of your module).

But what exactly does that
--follow-local-imports
option do?

From your home page, or from using its --help option, I am aware of the brief description:
follow imports for local files

But I still have no idea what it does.

Is it related to the local imports that I am already specifying in
--blocks --functions
?

Or is it something totally different?

First, Nicolas, thank you very much for writing this software and making it available on PyPi. I am grateful.

I just tried out findpydeps on one of my work repos, using a command line like this:

findpydeps -i . --blocks --functions --follow-local-imports --removal-policy 0 --strict --no-header > ./requirements_from_findpydeps.txt

I am confused about the results that findpydeps gave me.

In particular, my files have import lines involving opentelemetry like this:

from opentelemetry.exporter.cloud_trace import CloudTraceSpanExporter
from opentelemetry.instrumentation.logging import LoggingInstrumentor
from opentelemetry.propagate import set_global_textmap
from opentelemetry.propagators.cloud_trace_propagator import CloudTraceFormatPropagator
from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import Tracer, TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor, ConsoleSpanExporter

But findpydeps summarizes all those imports merely as
opentelemetry

In other words, instead of listing

opentelemetry.exporter.cloud_trace
opentelemetry.instrumentation.logging
etc

it seems as if findpydeps drops everything after the first '.' (i.e. period char).

That is a bug, right? I need the full package names to be listed, not just the first part.

I note that with opentelemetry, even if findpydeps gave me the fully parsed names, like opentelemetry.exporter.cloud_trace, that that would only be half the battle. For reasons that I cannot fathom, Google uses different names for the packages that you need to specify in your requirments.txt file. For example, instead of listing something like
opentelemetry-exporter-cloud-trace
in your requirments.txt, you actually need to use
opentelemetry-exporter-gcp-trace

Hi,

this is a great package you have here. I assume my wish isn't easy.

It would help a lot of I could see a dependency graph. I would like to know on what my dependencies are depending on and so on.

Use-case: One of my dependencies seems to import pandas or numpy. But I don't know which one.

I love that you use Python's AST to parse Python source files in this prokject.

I recently stumbled across this article: https://www.mattlayman.com/blog/2018/decipher-python-ast/

Check out its section "ast by example" or this code listing: https://www.mattlayman.com/2018/ast_example.py

This guy used the ast.NodeVisitor to extract data about imports in a very small amount of code.

Would using NodeVisitor in your code help simplify it too? (I have not thought deeply about this. Maybe features that your code supports, like not including imports in functions, might be hard to do if use a _NodeVisitor.)