Ubuntu – How to use the same Python for Windows and Linux on Windows subsystem for Linux

pythonwindows-subsystem-for-linux

I have Python 3.6 installed on my Windows computer. I installed the Windows Subsystem for Linux (WSL). When I type python into my Ubuntu terminal, I'm told I'm using Python 2.7 (which I imagine comes pre-installed on Ubuntu).

How can I use the same Python for both Windows and Linux, so that if I install a new package with pip from either, I can access it from either? I want the two systems to share the same Python.

It seems as though following something along the lines of creating an alias might work, but I'm pretty sure the pip command will remain the same (referring to Python 3.6 on Windows and Python 2.7 on Linux), as might other functionality.

Best Answer

You can use the version of python used in windows by typing in python.exe instead of python3. This is not recommended and there's no real reason to do so because you'll face several problems with

CR/LF line endings
Running python in this way does not preserve the path, hence, say you have test.py in the current WSL folder and run python.exe test.py. Python will be started in its root directory and will be unable to locate test.py

Python behaves identically, like in the case of pip freeze e.t.c and will produce the same output if you're running in the same virtualenv and hence just using the ubuntu version of python will work fine.

As of 18.04, WSL ubuntu has Python 3.6.5 preinstalled, and you can see both the windows and ubuntu python being used below

Related Solutions

Ubuntu – Running gnome-keyring on WSL (Windows Subsystem for Linux)

add at the end of ~/.bashrc

ssh-add -l &>/dev/null
if [ "$?" == 2 ]; then
  test -r ~/.gnome-keyring && \
    source ~/.gnome-keyring && \
    export DBUS_SESSION_BUS_ADDRESS GNOME_KEYRING_CONTROL SSH_AUTH_SOCK GPG_AGENT_INFO GNOME_KEYRING_PID

  ssh-add -l &>/dev/null
  if [ "$?" == 2 ]; then
    (umask 066; echo `dbus-launch --sh-syntax` > ~/.gnome-keyring; gnome-keyring-daemon >> ~/.gnome-keyring)
    source ~/.gnome-keyring && \
    export DBUS_SESSION_BUS_ADDRESS GNOME_KEYRING_CONTROL SSH_AUTH_SOCK GPG_AGENT_INFO GNOME_KEYRING_PID
  fi
fi

Credentials are automatically added to ssh-agent provided that both the public and private keys are inside ~/.ssh. Keychain storing applications such as mysql-workbench(requires Xming) also work.

You can ignore this warning on bash startup

gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used

source: https://www.reddit.com/r/bashonubuntuonwindows/comments/4yhch4/using_gnomekeyringdaemon_for_ssh_keys/

Ubuntu – Need to remove anaconda3 from $PATH

To completely remove anaconda from your path:

Check for the anaconda entry in both ~/.bashrc and ~/.bash_profile and remove the line:
```
export PATH="/home/sbendl/anaconda2/bin:$PATH"
```

For complete removal:

Remove the entries in the files stated above then get rid of the ~/anaconda2 dir.

And that should correct the issue.

Best Answer

Related Solutions

Ubuntu – Running gnome-keyring on WSL (Windows Subsystem for Linux)

Ubuntu – Need to remove anaconda3 from $PATH

Related Question