Skip to content

[FR] simplify gazelle_python.yaml #1890

@hunshcn

Description

@hunshcn

🚀 feature request

Relevant Rules

gazelle_python.yaml

Description

A clear and concise description of the problem or missing capability...

gazelle_python.yaml will list all libs on packages

    matplotlib.backend_tools: matplotlib
    matplotlib.backends: matplotlib
    matplotlib.backends.backend_agg: matplotlib
    matplotlib.backends.backend_cairo: matplotlib
    matplotlib.backends.backend_gtk3: matplotlib
    matplotlib.backends.backend_gtk3agg: matplotlib
    matplotlib.backends.backend_gtk3cairo: matplotlib
    matplotlib.backends.backend_gtk4: matplotlib
    matplotlib.backends.backend_gtk4agg: matplotlib
    matplotlib.backends.backend_gtk4cairo: matplotlib
    matplotlib.backends.backend_macosx: matplotlib
    matplotlib.backends.backend_mixed: matplotlib
    matplotlib.backends.backend_nbagg: matplotlib
    matplotlib.backends.backend_pdf: matplotlib
    matplotlib.backends.backend_pgf: matplotlib
...

I have a three lines only requirements.in

numpy
requests
seaborn

20 packages requirements.txt

but received a 110KB gazelle_python.yaml which has 2517 keys at .manifest.modules_mapping

It is too big.

Describe the solution you'd like

If you have a solution in mind, please describe it.

Can we simplify it and make gazelle_python.yaml have only top level package name?

In my shallow cognition, such a long imports seems meaningless.

I'd like to support it if I can.

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?

no

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions