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

Isolate externally-managed installation logic #33

Closed
jaimergp opened this issue Jun 13, 2024 · 1 comment · Fixed by #34
Closed

Isolate externally-managed installation logic #33

jaimergp opened this issue Jun 13, 2024 · 1 comment · Fixed by #34

Comments

@jaimergp
Copy link
Member

This needs to be executed as part of the conda recipe, so it would be nice if the import path doesn't need conda and friends (importlib.resources is enough).

That said, I should also look into whether some kind of python packaging configuration allows to indicate that EXTERNALLY-MANAGED should be placed in the parent of site-packages. This is different for every Python version, and also across Unix/Windows. This way we don't need custom code being run at build time.

@jaimergp
Copy link
Member Author

For now I just isolated the code we run to copy the file, but it would be nice(r) to have this handled natively.

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