Current problem

When running pyreverse against large projects, it's sometimes necessary to call pyreverse against different modules to create class graphs that are readable. However, tracing class ancestry outside the modules being analyzed, but within the project, is often still desired. The only way to do this today is to use --show-associated and --all-associated, but this will trace the ancestors for all modules, not just those in the same project.

Desired solution

Add an option to filter ancestors, either through regular expressions or by setting the parent module for the project, would be very useful for customizing what is shown in the graphs.

Additional context

No response