"sort: unrecognized option '--host'" error when debugging any file.

I’m not sure what the source of this problem is. Ptvsd seems to have inserted itself into every debug command, even after I removed the ‘attach’ option from launch.json. It makes it impossible to debug any Python file.

Environment data

• VS Code version: 1.27.1
• Extension version (available under the Extensions sidebar): 2018.8.0
• OS and version: CentOS 7
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda 5.2 Python 3.6.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): unknown
• Relevant/affected Python packages and their versions: NA

Actual behavior

Here is the terminal output when I hit the debug button:

$ cd /home/mgroeneveld/ml-climatology-explorer ; env "PYTHONIOENCODING=UTF-8" "PYTHONUNBUFFERED=1" "PYTHONPATH=/home/mgroeneveld/.vscode/extensions/ms-python.python-2018.8.0/pythonFiles/experimental/ptvsd" /home/mgroeneveld/anaconda3/bin/python -m ptvsd --host localhost --port 42912 /home/mgroeneveld/ml-climatology-explorer/main.py
sort: unrecognized option '--host'

Expected behavior

I expect VS Code to enter debugging mode.

Steps to reproduce:

1. Click debug button (integrated terminal mode) with at least 1 breakpoint in any trivial python file.

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

None

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

None

[groeneveld]

It turned out to be a problem with the default .bashrc provided on my computer.

[groeneveld]

@d3r3kk

$ /home/mgroeneveld/anaconda3/bin/python -c 'import sys; print([sys.executable, sys.version])'
['/home/mgroeneveld/anaconda3/bin/python', '3.6.6 |Anaconda custom (64-bit)| (default, Jun 28 2018, 17:14:51) \n[GCC 7.2.0]']

['/home/mgroeneveld/anaconda3/bin/python3', '3.6.6 |Anaconda custom (64-bit)| (default, Jun 28 2018, 17:14:51) \n[GCC 7.2.0]']

@DonJayamanne Great question! I don’t and have no idea why it’s appearing in this context.

$ env "ABC=1234" date
sort: cannot read: ABC=1234: No such file or directory

$ date
Tue Sep 18 16:29:55 EDT 2018