Skip to content

Allow specification of Python executable #52

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

Closed
jjtolton opened this issue Jan 20, 2020 · 2 comments · Fixed by #53
Closed

Allow specification of Python executable #52

jjtolton opened this issue Jan 20, 2020 · 2 comments · Fixed by #53

Comments

@jjtolton
Copy link
Contributor

Currently the Python3 executable path is hardcoded to "python3". I propose we allow the executable to be specified via :python-executable in py/initialize!. On my system, Python3.6 always gets picked up first even though Python3.7 is available because Python3.6 is my current system alternative.

This change should also allow use of Python virtual environments.

@gigasquid
Copy link
Contributor

Whether libpython-clj works with a virtual environment has come up a lot in general questions/ interactions. I think this will be very beneficial. 🎉

@orolle
Copy link
Contributor

orolle commented Jan 21, 2020

I try to get libpython-clj work with anaconda on windows. The windows PATH environment variable for clojure.java.shell/sh is handled a little bit different compared to Linux & Mac. Thus the hardcoded "python3" makes it impossible to execute anything with clojure.java.shell/sh. Being able to parameterize the python-executable would work around windows specifics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants