Replies: 3 comments 15 replies
-
|
this is a curious error, something must have gone wrong along the way can you email me the .bash_profile file (don't attach it here since you might have information in there that should not be public) |
Beta Was this translation helpful? Give feedback.
-
|
Actually, I found that my Python and doctor.py are not in the same directory and then I ran doctor.py and got this result. |
Beta Was this translation helpful? Give feedback.
-
|
I guess:Maybe the tools were installed, but that the PATH wasn’t set correctly. Even though I activated (bioinfo), the micromamba shell hook didn’t take effect in the shell, so the PATH didn’t switch to bioinfo/env/bin. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description of the problem
After installing Biostar Handbook software using the provided installation script, I encountered two issues:
When running micromamba activate bioinfo, I see the message -bash: syntax error near unexpected token '('. However, the prompt does change to (bioinfo), so it seems partially activated.
When running doctor.py inside the environment, I get the error: /usr/bin/env: 'python': No such file or directory.
Steps to reproduce
Commands I executed and their outputs:
Expected behavior
Activating the environment should not trigger a bash syntax error.
Running doctor.py inside the bioinfo environment should work normally and detect the Python interpreter.
Actual behavior
Bash shows -bash: syntax error near unexpected token '('.
Running doctor.py fails with /usr/bin/env: 'python': No such file or directory.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions