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
rebuild pip wheels with manylinux #566
Comments
this is really dumb, but after reading PEP-513 and looking at what TF and others do, all the user-failures came down to the name of the file. I fixed the filenames on the website pip install commands. I'm still going to setup manylinux wheels, but de-prioritizing this down to low. |
If you don't support pypi, why send users here and not to http://pytorch.org/ ?
etc, depending on the platform |
hi guys, I got an error when I execute the second command "pip install torchvision", and the error report is
The problem that confused me is that "/tmp/pip-build-hho2Nf/torch/setup.py", where the error happens, seems to be a temporary file and I don't know what's in its line 11, so I can't start to debug the problem. Can any one tell me what is this setup.py file? My computer needs proxy, but I don't think this is relevant because pip command works fine with other packages on my computer. Meanwhile, when I downloaded the torchvision whl file and try to install it locally, the same error happens. My operating system is Linux mint 18, a derivative of Ubuntu 16 LTS. It strange that these two pip command in my laptop(also a mint 18 system) works fine. Thank you for you help and time. |
@Lowpassfilter first install pytorch, and then install torchvision |
@soumith do you mean the following two commands:
everything goes fine with the first command, however, the second command will produce the error I mentioned above. |
problem is that it is using a cached file |
I came across the same problem as Lowpossfilter, and this did not work |
so uuuh. what's the status here? Those instructions don't work for me for me with the same exact error on the torchvision step: RuntimeError: PyTorch does not currently provide packages for PyPI (see status at #566)
|
@soumith I have done it, and this didn't work for me. |
clueless, what are we supposed to do ? |
That's not the problem here. The
That will at least get past the issue in the
I'm on a quite standard Ubuntu install with gcc 4.8.4, so maybe current master is also not in an installable state right now. |
looks like the error is back for me. What is the root of this problem? How can we find it? |
same here! |
yeah well, just go to: and install it using the given address, in my case (osx 2.7 no cuda) was: pip install http://download.pytorch.org/whl/torch-0.1.12.post2-cp27-none-macosx_10_7_x86_64.whl have fun! |
Those install instructions do not work for everybody. I've just come across two more machines (of colleagues of mine) that have this error. It seems to occur at random and the error message is entirely unhelpful. It seems odd that this bug is tagged "low priority" considering how many people use pip to install things. Difficulty of installation is the number one thing I've seen turn away students and amateurs from choosing a first tool to learn. Perhaps I'm not experienced enough to say, but this seems like something that affects the level to which pytorch will be adopted in the future. How can we help to resolve this? |
Agree with @ThaHypnotoad. I've been waiting for this fix for more than a month now. During the same month, I've gotten more comfortable with Tensorflow, which makes my switch to pytorch doubtful. Will opening a new 'issue' move things? |
I had the same problem and I've found the solution. Basically, pip is trying to run "pip install torch" because torch is listed in the dependencies and it does not detect the previously build version with wheel. So just run "pip install --no-deps torchvision" and it should work. And this could be permanently fixed by updating the setup.py file in torchvision repository. |
I can confirm that @DjAntaki s solution works on every machine I've seen have this issue on. |
@DjAntaki Thanks! |
Still now I am not able to install pytorch ~ pip install http://download.pytorch.org/whl/cu75/torch-0.2.0.post1-cp36-cp36m-manylinux1_x86_64.whl
pip install torchvision And the output which I am getting is:
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-Qy2Ipn/torch/ I am using Ubuntu 16.04 LTS. Is there any other way out ? |
`RuntimeError: PyTorch does not currently provide packages for PyPI (see status at #566). Please follow the instructions at http://pytorch.org/ to install with miniconda instead. |
@salavi pytorch doesn't provide packages for 3.4. It only provides packages for 3.5, 3.6, 2.7 at the moment (and 3.7 from next release) |
win10 |
import torch works on terminal,but unwork on pycharm(win7) |
Where can I find a list for wheels???!! Older versions for ubuntu |
hi |
hi ,I am in Win10 .Python version is 3.6.5. pip version is 19.0.3 c:>pip install --no-deps torch -i https://pypi.mirrors.ustc.edu.cn/simple/
Command "python setup.py egg_info" failed with error code 1 in C:\Users\65140\AppData\Local\Temp\pip-install-417u5z60\torch\ |
I have solved this problem. pip3 install http://download.pytorch.org/whl/cpu/torch-0.4.1-cp36-cp36m-win_amd64.whl |
This problem, I mean -> RuntimeError: PyTorch does not currently provide packages for PyPI (see status at #566). -> in my case (on Windows) was solved by installing the 64-bit version of Python and rewriting path variables to Python and its libraries. After updating the path try rebooting. And after that I could freely install PyTorch without any errors. |
正在尝试该方法,不是是否可以解决这个问题。 |
(pytorch) C:\Windows\system32>pip install torch
ERROR: Command "python setup.py egg_info" failed with error code 1 in C:\Users\PanPan\AppData\Local\Temp\pip-install-a6nog5b5\torch\ |
@Man1029, you can get latest torch or torchvision package through command: |
Thanks buddy! |
For install instructions please go to http://pytorch.org
This is needed to work across many different linux distros, new and old.
manylinux will build the wheel on a CentOS5 (yes!) Docker machine.
The text was updated successfully, but these errors were encountered: