Skip to content

Separate explicit dependencies and implicit dependencies in API match #144

Open
@CJ-Wright-Citadel

Description

@CJ-Wright-Citadel

Some dependencies are explicit, you are importing a symbol from a module.
Some dependencies are implicit, you are importing a symbol from a module which is a shim for another symbol.

I'm not certain if implicit dependencies are handled by many package managers properly, since they are nominally provided by the explicit dependency that supplies the shim but may have specific version constraints that the depending package doesn't supply.

For instance from abc import abs where abc is getting abs from numpy but abs is a new symbol and is only available in the most recent version of numpy. Since abc may do a star import, it doesn't explicitly have a version requirement on numpy but downstream may.

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