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

Can we use pytorch channel? #17

Closed
fecet opened this issue Jul 12, 2023 · 1 comment
Closed

Can we use pytorch channel? #17

fecet opened this issue Jul 12, 2023 · 1 comment
Labels
question Further information is requested

Comments

@fecet
Copy link

fecet commented Jul 12, 2023

Comment:

I'm not familier with conda-forge, are we restricted to use conda-forge packages? Otherwise can we use pytorch provided from its own channel so we can also get pytorch-nightly https://anaconda.org/pytorch-nightly/pytorch

@fecet fecet added the question Further information is requested label Jul 12, 2023
@weiji14
Copy link
Member

weiji14 commented Aug 11, 2024

Hi @fecet, so sorry for the late reply. I'm assuming that you've managed to install a newer version of Pytorch from conda-forge already (e.g. 2.3.1), so not sure if this issue is still relevant?

In general, we discourage mixing channels because there could be incompatibilities in the builds across different channels causing weird undefined symbol errors (see https://conda-forge.org/docs/user/tipsandtricks/#using-multiple-channels for more information). For the Pytorch library in particular, some of the differences between the conda-forge and pytorch channel are mentioned at conda-forge/pytorch-cpu-feedstock#218 (see also my comment at conda-forge/pytorch3d-feedstock#10 (comment)). I'll close this issue for now, but feel free to reopen if you need additional clarification, or comment on the thread in pytorch-cpu-feedstock.

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

No branches or pull requests

2 participants