-
Notifications
You must be signed in to change notification settings - Fork 75
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
uninitialized constant PyCall::LibPython::Helpers #145
Comments
You need to specify the path of python executable in |
Hi, Thanks for response. I had added the following value to PYTHON env var.
but still I could see issues as below
Really appreciate your response. Thanks |
Hm. Alright. Tried a few things, none of them worked. Dug around in pycall's code a bit. It looks like it's asking for ENV["PYTHON"] but not finding it. Actually, I had no idea that this is variable was here. Anyway, after I added a PYTHON path to the variable list (make sure it's not SYSTEM variables, at the bottom of the environmental variable screen, but the ENVIRONMENTAL variables at the top), my scripts that used Pycall started working again. Thank you. |
Hmm. It seems to work with one python module (genanki) and not another (aeneas), I'm getting another const missing error, The solution is probably to add more variables.
|
Oh god. It's looking for a variable called PYTHONHOME in my environmental variables. It's not there, and then... it looks like it's deciding to use_conda, except I don't have anaconda. Hmm. In my head: "He swallowed the Anaconda to shave the Yak; He swallowed the Yak to catch the Python; To run on Ruby; To catch the fly; I don't know why he swallowed the fly..." |
Eventually, I just gave up and set up an environment on WSL, like I probably should have done in the first place. |
Environment Variables:
Also added python location to environment variables.
The text was updated successfully, but these errors were encountered: