Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate explicit dependencies and implicit dependencies in API match #144

Open
CJ-Wright-Citadel opened this issue Jul 29, 2021 · 0 comments

Comments

@CJ-Wright-Citadel
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant