-
Notifications
You must be signed in to change notification settings - Fork 189
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
Build works with PYTHON="python" but fails with explicit PYTHON="/path/to/python" #710
Comments
The stacktrace says that the failure happens at Lines 82 to 85 in cf01bf0
Maybe related to these issues? |
Thanks, yea I think its JuliaPy/Conda.jl#146 because on this system I'm using a non-root environment, and indeed if I run the code snippet in the first comment there, its "still trying to install miniconda". I'll close this in favor of that. Let me know if you know of any workarounds until that might be fixed. |
Or maybe I should leave this open? I suppose unrelated to that, its a little weird on the PyCall side for there to be any difference if you specify python explicitly or not, if the paths resolve to the same thing in the end? I'll leave it up to you guys. |
Yeah, I think But I don't feel like fixing it ATM personally (fixing Conda.jl has higher priority) so I don't mind if it is closed again. |
As per the title, this works
but putting the path explicitly fails:
with the log attached below. Any ideas what might be happening? I'm unable to reproduce on other systems. This is Julia v1.2, Conda v1.3.0, PyCall v1.91.2.
The text was updated successfully, but these errors were encountered: