You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start a Azure Function write in Python, I receive the following message and can't run it
Starting worker process:python /Users/adriano/.vscode/extensions/ms-python.python-2019.11.49689/pythonFiles/lib/python/new_ptvsd/no_wheels/ptvsd --default --host 127.0.0.1 --port 9091 --wait "/usr/local/Cellar/azure-functions-core-tools/2.7.1846/workers/python/3.7/OSX/X64/worker.py" --host 127.0.0.1 --port 50506 --workerId 7ccf8740-490c-40d3-8e11-6a8c1a5f074b --requestId af4c3963-eebf-491a-8006-1d4ede1026b5 --grpcMaxMessageLength 134217728
[20/11/2019 18:59:45] python process with Id=4667 started
[20/11/2019 18:59:45] ptvsd 5.0.0a7
[20/11/2019 18:59:45] See https://aka.ms/ptvsd for documentation.
[20/11/2019 18:59:45] Usage: ptvsd [--client] --host
Seems like the latest ptvsd 5.0.0a7 drops the support for the --default flag.
There's an issue tracked by the vscode extension team microsoft/vscode-azurefunctions#1743.
When I start a Azure Function write in Python, I receive the following message and can't run it
[--port ]Starting worker process:python /Users/adriano/.vscode/extensions/ms-python.python-2019.11.49689/pythonFiles/lib/python/new_ptvsd/no_wheels/ptvsd --default --host 127.0.0.1 --port 9091 --wait "/usr/local/Cellar/azure-functions-core-tools/2.7.1846/workers/python/3.7/OSX/X64/worker.py" --host 127.0.0.1 --port 50506 --workerId 7ccf8740-490c-40d3-8e11-6a8c1a5f074b --requestId af4c3963-eebf-491a-8006-1d4ede1026b5 --grpcMaxMessageLength 134217728
[20/11/2019 18:59:45] python process with Id=4667 started
[20/11/2019 18:59:45] ptvsd 5.0.0a7
[20/11/2019 18:59:45] See https://aka.ms/ptvsd for documentation.
[20/11/2019 18:59:45] Usage: ptvsd [--client] --host
[20/11/2019 18:59:45] [--wait]
[20/11/2019 18:59:45] [--no-subprocesses]
[20/11/2019 18:59:45] [--log-dir ] [--log-stderr]
[20/11/2019 18:59:45] | -m | -c
| --pid
[20/11/2019 18:59:45] Error: unrecognized switch --default
The text was updated successfully, but these errors were encountered: