Changing the default python version of RStudio [closed]
In RStudio, usinglibrary('PythonInR'), and then usingPythonInR::pyConnect()
it shows that the location of the python called is /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7,
however there is no such package in my mac because I've deleted it.
I just want to know how to change the default python path of RStudio when I use PythonInR?
python r
edited Nov 21 at 8:57
Christian
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
closed as too broad by Ankit Agarwal, Owen Pauling, EdChum, Nguyễn Thanh Tú, Rob Nov 21 at 14:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
In RStudio, usinglibrary('PythonInR'), and then usingPythonInR::pyConnect()
it shows that the location of the python called is /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7,
however there is no such package in my mac because I've deleted it.
I just want to know how to change the default python path of RStudio when I use PythonInR?
python r
edited Nov 21 at 8:57
Christian
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
closed as too broad by Ankit Agarwal, Owen Pauling, EdChum, Nguyễn Thanh Tú, Rob Nov 21 at 14:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
have u tried any groups or google?
– sai saran
Nov 21 at 8:42
add a comment |
In RStudio, usinglibrary('PythonInR'), and then usingPythonInR::pyConnect()
it shows that the location of the python called is /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7,
however there is no such package in my mac because I've deleted it.
I just want to know how to change the default python path of RStudio when I use PythonInR?
python r
edited Nov 21 at 8:57
Christian
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
In RStudio, usinglibrary('PythonInR'), and then usingPythonInR::pyConnect()
it shows that the location of the python called is /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7,
however there is no such package in my mac because I've deleted it.
I just want to know how to change the default python path of RStudio when I use PythonInR?
python r
python r
edited Nov 21 at 8:57
Christian
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
edited Nov 21 at 8:57
Christian
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
edited Nov 21 at 8:57
Christian
10.7k2894156
edited Nov 21 at 8:57
Christian
10.7k2894156
edited Nov 21 at 8:57
Christian
10.7k2894156
10.7k2894156
asked Nov 21 at 8:23
TahYM
161
asked Nov 21 at 8:23
TahYM
161
asked Nov 21 at 8:23
TahYM
161
161
closed as too broad by Ankit Agarwal, Owen Pauling, EdChum, Nguyễn Thanh Tú, Rob Nov 21 at 14:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Ankit Agarwal, Owen Pauling, EdChum, Nguyễn Thanh Tú, Rob Nov 21 at 14:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
have u tried any groups or google?
– sai saran
Nov 21 at 8:42
add a comment |
have u tried any groups or google?
– sai saran
Nov 21 at 8:42
have u tried any groups or google?
– sai saran
Nov 21 at 8:42
have u tried any groups or google?
– sai saran
Nov 21 at 8:42
add a comment |
1 Answer
1
active
oldest
votes
PythonInR has parameters that let you specify your python environment that you want to use with R/R Studio in a variety of ways -
library('PythonInR')
pyConnect(pythonExePath = "C:/ProgramData/Anaconda3/python.exe", dllDir = "C:/ProgramData/Anaconda3", pythonHome = "C:/ProgramData/Anaconda3")`
From the documentation
Arguments
pythonExePatha character containing the path to
"python.exe" (e.g. "C:Python27python.exe")
dllDiran optional
character giving the path to the dll file. Since the dll file is
normally in a system folder or in the same location as python.exe,
this parameter is almost never needed!
pythonHomean optional
character giving the path to PYTHONHOME. On Windows by default
PYTHONHOME is the folder where python.exe is located, therefore this
parameter is normally not needed.
dllNamea character giving the name
of the dll file (e.g.d "python27.dll"). majorVersion an integer giving
the major Python version (e.g. 2 or 3).
pyArcha character giving the
Python architecture, i.e. "32bit" or "64bit". useCstdout a logical
indicating if the C stdout should be used or the stout should be
redirected at a Python level.
TL; DR
Use pythonExePath to specify the python exe location and give it a go. Try subsequent parameters if things still don't work
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
PythonInR has parameters that let you specify your python environment that you want to use with R/R Studio in a variety of ways -
library('PythonInR')
pyConnect(pythonExePath = "C:/ProgramData/Anaconda3/python.exe", dllDir = "C:/ProgramData/Anaconda3", pythonHome = "C:/ProgramData/Anaconda3")`
From the documentation
Arguments
pythonExePatha character containing the path to
"python.exe" (e.g. "C:Python27python.exe")
dllDiran optional
character giving the path to the dll file. Since the dll file is
normally in a system folder or in the same location as python.exe,
this parameter is almost never needed!
pythonHomean optional
character giving the path to PYTHONHOME. On Windows by default
PYTHONHOME is the folder where python.exe is located, therefore this
parameter is normally not needed.
dllNamea character giving the name
of the dll file (e.g.d "python27.dll"). majorVersion an integer giving
the major Python version (e.g. 2 or 3).
pyArcha character giving the
Python architecture, i.e. "32bit" or "64bit". useCstdout a logical
indicating if the C stdout should be used or the stout should be
redirected at a Python level.
TL; DR
Use pythonExePath to specify the python exe location and give it a go. Try subsequent parameters if things still don't work
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
add a comment |
PythonInR has parameters that let you specify your python environment that you want to use with R/R Studio in a variety of ways -
library('PythonInR')
pyConnect(pythonExePath = "C:/ProgramData/Anaconda3/python.exe", dllDir = "C:/ProgramData/Anaconda3", pythonHome = "C:/ProgramData/Anaconda3")`
From the documentation
Arguments
pythonExePatha character containing the path to
"python.exe" (e.g. "C:Python27python.exe")
dllDiran optional
character giving the path to the dll file. Since the dll file is
normally in a system folder or in the same location as python.exe,
this parameter is almost never needed!
pythonHomean optional
character giving the path to PYTHONHOME. On Windows by default
PYTHONHOME is the folder where python.exe is located, therefore this
parameter is normally not needed.
dllNamea character giving the name
of the dll file (e.g.d "python27.dll"). majorVersion an integer giving
the major Python version (e.g. 2 or 3).
pyArcha character giving the
Python architecture, i.e. "32bit" or "64bit". useCstdout a logical
indicating if the C stdout should be used or the stout should be
redirected at a Python level.
TL; DR
Use pythonExePath to specify the python exe location and give it a go. Try subsequent parameters if things still don't work
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
add a comment |
PythonInR has parameters that let you specify your python environment that you want to use with R/R Studio in a variety of ways -
library('PythonInR')
pyConnect(pythonExePath = "C:/ProgramData/Anaconda3/python.exe", dllDir = "C:/ProgramData/Anaconda3", pythonHome = "C:/ProgramData/Anaconda3")`
From the documentation
Arguments
pythonExePatha character containing the path to
"python.exe" (e.g. "C:Python27python.exe")
dllDiran optional
character giving the path to the dll file. Since the dll file is
normally in a system folder or in the same location as python.exe,
this parameter is almost never needed!
pythonHomean optional
character giving the path to PYTHONHOME. On Windows by default
PYTHONHOME is the folder where python.exe is located, therefore this
parameter is normally not needed.
dllNamea character giving the name
of the dll file (e.g.d "python27.dll"). majorVersion an integer giving
the major Python version (e.g. 2 or 3).
pyArcha character giving the
Python architecture, i.e. "32bit" or "64bit". useCstdout a logical
indicating if the C stdout should be used or the stout should be
redirected at a Python level.
TL; DR
Use pythonExePath to specify the python exe location and give it a go. Try subsequent parameters if things still don't work
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
PythonInR has parameters that let you specify your python environment that you want to use with R/R Studio in a variety of ways -
library('PythonInR')
pyConnect(pythonExePath = "C:/ProgramData/Anaconda3/python.exe", dllDir = "C:/ProgramData/Anaconda3", pythonHome = "C:/ProgramData/Anaconda3")`
From the documentation
Arguments
pythonExePatha character containing the path to
"python.exe" (e.g. "C:Python27python.exe")
dllDiran optional
character giving the path to the dll file. Since the dll file is
normally in a system folder or in the same location as python.exe,
this parameter is almost never needed!
pythonHomean optional
character giving the path to PYTHONHOME. On Windows by default
PYTHONHOME is the folder where python.exe is located, therefore this
parameter is normally not needed.
dllNamea character giving the name
of the dll file (e.g.d "python27.dll"). majorVersion an integer giving
the major Python version (e.g. 2 or 3).
pyArcha character giving the
Python architecture, i.e. "32bit" or "64bit". useCstdout a logical
indicating if the C stdout should be used or the stout should be
redirected at a Python level.
TL; DR
Use pythonExePath to specify the python exe location and give it a go. Try subsequent parameters if things still don't work
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
edited Nov 21 at 8:55
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
answered Nov 21 at 8:50
Vivek Kalyanarangan
4,6331826
4,6331826
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
add a comment |
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
thx. But I've already tried this method in another laptop of windows system and it did work. But it just could not work when applied to my macbook, it still connects to the default python path.
– TahYM
Nov 21 at 9:32
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python.
– Florian
Nov 22 at 10:15
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
On Windows you can change the Python version when connecting to Python. On Unix the Python version is fixed after the installation. This is a result using different linking paradigms. On Windows explicit linkage is used on Linux static linkage is used. For you as Unix user this means you have to reinstall your PythonInR however you also need the correct development headers present. On Debian Sys.setenv(USESPECIALPYTHONVERSION="python3") install.packages("PythonInR") is sufficient to change from Py 2 to Py 3 given that also the dev headers of Python 3 are installed.
– Florian
Nov 22 at 11:09
add a comment |
have u tried any groups or google?
– sai saran
Nov 21 at 8:42