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

Collision in package name with colour-science #62

Open
hop-soellingeraj opened this issue Aug 2, 2022 · 1 comment
Open

Collision in package name with colour-science #62

hop-soellingeraj opened this issue Aug 2, 2022 · 1 comment

Comments

@hop-soellingeraj
Copy link

There is a collision in package name, both have package name == colour
This package and https://www.colour-science.org/installation-guide/

If the latter is installed in the PYTHONPATH, all attempts to import from colour import Color will fail.

@KelSolaar
Copy link

Because we, colour-science/colour are a package and vaab/colour is a module, we take precedence as packages are imported first. I'm thinking to solve this issue by importing vaab/colour into our namespace if it is present on sys.path. It is admittedly gross but this should fix the issues people are having.

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

2 participants