-
Notifications
You must be signed in to change notification settings - Fork 334
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
Trouble with conda_list()
, pls change back to behavior in reticulate 1.0.0
#100
Comments
The problem is that parsing Anaconda environments from the text generated for user display (as opposed to JSON) led to numerous similar error conditions (as that text isn't really intended to be machine parsed). So if I revert that change I'm "un-fixing" a bunch of bugs. In your case it looks like an error is being thrown when calling Could you try again with the latest from master to see if we successfully ignore the error condition in |
Hey JJ, Warning message:
running command '"C:\Users\pi37pat\AppData\Local\CONTIN~1\ANACON~1/Scripts/conda.exe" info --json' had status 1 But that's ok, I simply suppress it. Loads of thanks again! |
Just added a |
Perfect, thanks again! |
Hey there,
I'm on Windows and have been using reticulate in combination with the Python binary shipped by QGIS since January 2017 for the **RQGIS ** package. This has worked like a charm (thanks!!, and still does under UNIX) until your latest update.
Running
Sys.getenv("PATH")
yields in my case:Subsequently, running
py_discover_config()
works, and results in:However, as soon as I change PYTHONHOME with
Sys.setenv(PYTHONHOME = "C:\\OSGeo4W64\\apps\\Python27")
,py_discover_config()
fails saying:As I have said before, everything just worked fine until your latest update. Digging a bit deeper, I found the culprit to be
reticulate:::python_environment_versions()
and within this function it isconda_list()
causing trouble (by the way, I actually do not want to use Anaconda at all, all the contrary, I want to make sure to not use Anaconda at all.) Well, basically, what I am asking is if you could change the function's behavior back to what it used to be in reticulate 1.0.0.The text was updated successfully, but these errors were encountered: