-
Notifications
You must be signed in to change notification settings - Fork 0
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
Python dependency installation error #12
Comments
Thanks for sharing this and for troubleshooting installation with me. The first set of warning messages are an R package installation issue (see r-lib/remotes#368). It's best to install R packages in a fresh R session before any are loaded (when possible). I'm not sure if those are causing issues for you but it's a different issue than the python related error from DO.utils. It seems that the pyDOID python package is still not available to DO.utils. Can you tell me a bit more about your Python setup? Did you have an installation of Python before installing DO.utils? Can you share with me the results of running |
I installed the package in a virtual environment called myenv using miniconda.
I installed Python before, and the image below shows python environments that can be linked to R.
|
Hmmm... that is strange. It seems like you should be good to go. I have noticed in the past that reticulate will sometimes activate the wrong environment and that may be what it's doing here. The only way I've found to get reticulate to use a consistent environment is to ensure the environment variable RETICULATE_PYTHON is set. This setting seems to override everything else. Can you provide the output of If you restart R to get a fresh session, then set the RETICULATE_PYTHON variable with |
Looking at the reticulate issue tracker there are quite a few issues surrounding installation and some of these have been resolved in later releases than the 1.23 release used by DO.utils, so I'm going to bump the version of reticulate used by DO.utils to the latest release (v1.28) in the hope that it will improve things. In general, I've been keeping an eye on tensorflow for how to ensure proper install. I noticed that they are still using an approach for installation that relies on a custom install function ( Sorry you're having so much trouble with this. |
This appears to be a problem a number of R packages that depend on python packages are having (rstudio/reticulate#997). I need to check whether updating the reticulate version has fixed the problem but if it didn't I discovered a pretty simple workaround. Anyone who installs miniconda when prompted should have an |
I tried to Does it mean that DO.utils needs to be reinstalled in a virtual environment called r-retriculate? |
DO.utils doesn't need to be in any specific environment but the python package(s) it sometimes uses do. I tested this recently on a Mac and it automatically created the r-reticulate virtual environment but didn't complete the install of pyDOID. It did work for me to simply tell it to install. In order to install more packages, you do have to have a virtual environment created and activated but it looks like you already do. Yours is just named myenv. Did the install of pyDOID seem to work when you ran Since you had issues with the initial install and had all those 'problem copying...' errors it's possible that you have some corrupted files that are causing issues. It might be best to try re-installing from scratch. I'll try installing DO.utils on a PC later in the week and let you know what I get. |
yes, I did. I get a message that it's already installed, but it still doesn't work. Thank you for your help. It's hard work, so I hope it's solved well.
|
Hi,
This warning message (above) appears after installing DO.utils.
There was nothing wrong with loading the DO.utils library.
It seemed to be going well, but there seemed to be a problem with installing the "adeft" packages, so I manually proceeded with setup.py and solved it.
The RStudio also outputs TRUE.
It seemed like the package problem was being solved, but... It doesn't work :(
The text was updated successfully, but these errors were encountered: