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

When I run the 2nd command from the Readme, I get the error „No module named torch” #105

Closed
sosasees opened this issue Sep 27, 2020 · 4 comments

Comments

@sosasees
Copy link

When I run the 2nd command from the Readme, the command being

python -c "import torch; print(torch.__version__)"

, I get this error as the output of the command:

Traceback (most recent call last):
File "", line 1, in
ImportError: No module named torch

. How do I fix this error so that I can install DAIN on my Linux Computer?

@sosasees sosasees changed the title When I run a command from the Readme, I get the error „No module named torch” When I run the 2nd command from the Readme, I get the error „No module named torch” Sep 27, 2020
@AlphaGit
Copy link
Contributor

@sosasees Hi! That step is to verify that you have PyTorch as a module available. The error demonstrates that you don't. As such, you'd need to install PyTorch 1.0.0 or above.

@iBobbyTS
Copy link

pip install torch==1.4.0

PyTorch 1.4 is the latest version compile with DAIN, it's faster than 1.0.0

@sosasees
Copy link
Author

sosasees commented Sep 27, 2020

Thanks for the Installation Command.
I must've taken a break not long enough, because I didn't see it at the beginning of the Readme.

I suggest changing the recommended PyTorch version from 1.0.0 to 1.0.4 because of @iBobbyTS,
but I don't exactly know how to communicate that without:

  • removing the information that PyTorch 1.0.0 is also compatible without clunkiying up the wording

@iBobbyTS
Copy link

In the README, it says it needs to be torch>=1.0.0. Torch 1.5.0 causes errors when building CUDAExtension. Torch 1.4.0 works, and it does a faster job than 1.0.0. There will be warnings in 1.4.0, just use a warning filter to remove them, not a big deal.

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

3 participants