Closed mturilli closed 10 years ago
Hmm, this is actually working for me, in a fresh virtualenv. And so it should, because what pip seems to do is to clone the full repo to virtualenv/src/troy, and then we are back to the normal install from git repository. I am not sure how to debug this, will try to reproduce on other systems. Do you have any idea? On what machine did you try -- I assume this is your laptop?
It is also strange because we used that during the tutorial, and it worked ok. Also, it is the same mechanism as in sagapilot and radical.utils -- do those work for you?
Thanks, A.
It it maybe related to https://github.com/saga-project/saga-python/issues/306 ?
On 05 Mar 2014, at 21:33 , Andre Merzky notifications@github.com wrote:
Hmm, this is actually working for me, in a fresh virtualenv. And so it should, because what pip seems to do is to clone the full repo to virtualenv/src/troy, and then we are back to the normal install from git repository. I am not sure how to debug this, will try to reproduce on other systems. Do you have any idea? On what machine did you try -- I assume this is your laptop?
It is also strange because we used that during the tutorial, and it worked ok. Also, it is the same mechanism as in sagapilot and radical.utils -- do those work for you?
Thanks, A.
— Reply to this email directly or view it on GitHub.
Ach, of course! Thanks Mark!
Good news is that the saga-python ticket can be closed. The bad news is that it doesn't seem to relate to this problem after all... :/ Thanks though!
I managed to test this again (on my laptop) and it did not fail. Shall we close it?
I would be happy to close it, obviously... If it ever happens again though, please try to create a recipe for reproduction, if possible -- that is not something I want to have lingering around...
Thanks, Andre.
Devel branch:
Master branch: