Closed mastak closed 9 years ago
Hi Igor,
Thanks for pointing this out, that is indeed not very user friendly. I just published pip-accel 0.22.3 which should resolve the issue you encountered. Can you try it out and let me know whether this is better? Thanks!
Hi Peter,
Traceback disappeared, but the problem is still there.
The thing in that I am using pip-accel inside Dockerfile (instructions for docker). And pip-accel with empty file return a non-zero code:
"error":"The command [/bin/sh -c pip-accel install -r /opt/checkio_mission/python_27/requirements.txt] returned a non-zero code: 1
And all build breaks down. But pip works fine in that case.
Hi Igor,
Thanks for the follow up, I didn't realize your concern was the exit code instead of just the printing of the traceback (you didn't mention the exit code before). I agree that pip-accel should be compatible with pip in this case. I'll try to fix this today.
Yes, it was my mistake, sorry.
PS Thanks for quick reply.
Hi Igor,
The problem you reported should now be resolved: The traceback is gone and the exit code is the same as pip (0). Sorry it took so long, especially after I said I'd try to fix this the same day - life got in the way of my open source projects (it does that sometimes :-). If you can confirm whether you agree the problem is resolved that would be appreciated; you can close this issue if so. Thanks for pointing out this incompatibility with pip!
I'm going to close this issue now because the problem reported here has been fixed for a while now. Thanks for the feedback!
Pip just return a simple message. But when i try install requirements from empty file, pip-accel generate exception: