Skip to content

Wrong Gazelle mappings after upgrading to 1.8 #3528

@psalaberria002

Description

@psalaberria002

We are seeing a wrong change for a specific dependency in gazelle_python.yaml after upgrading the Gazelle plugin from 1.6 to 1.8.1.

Image
# requirements.in
bosdyn-client==5.0.1.2
bosdyn-orbit==5.0.1.2

Build error:

E   ModuleNotFoundError: No module named 'bosdyn.client'

I suspect it was introduced by https://github.com/bazel-contrib/rules_python/pull/3415/changes

Adding manual resolve directives solves the build errors, but that's just a workaround.

# gazelle:resolve py bosdyn.api @python_deps//bosdyn_api
# gazelle:resolve py bosdyn.bddf @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.client @python_deps//bosdyn_client
# gazelle:resolve py bosdyn.deprecated @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.geometry @python_deps//bosdyn_core
# gazelle:resolve py bosdyn.util @python_deps//bosdyn_core

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions