You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a library which I hope to share with users - I'm using poetry for dependency management within my pyproject.toml.
What's the best practices surrounding facilitating users to use a GPU-enabled variant of JAX when they install such a library? Has anyone investigated this before?
I think roughly a user can always just overload their current Python environment by first installing my library, and then using pip to install a GPU-enabled variant of JAX.
I'm curious if that's basically how people solve this issue -- and if there's nothing better.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all!
I'm developing a library which I hope to share with users - I'm using
poetry
for dependency management within mypyproject.toml
.What's the best practices surrounding facilitating users to use a GPU-enabled variant of JAX when they install such a library? Has anyone investigated this before?
I think roughly a user can always just overload their current Python environment by first installing my library, and then using
pip
to install a GPU-enabled variant of JAX.I'm curious if that's basically how people solve this issue -- and if there's nothing better.
Beta Was this translation helpful? Give feedback.
All reactions