How does this work?

[rahulbansal16]

Before I stumbled upon your solutions. I was doing this.

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        
        {
            "name": "Python: Current File",
            "envFile": "${workspaceFolder}/.env",
            "type": "python",
            "request": "launch",
            "program": "${workspaceFolder}/env/Scripts/functions-framework-python.exe",
            "args": ["--target","trainMBOX","--debug"],
            "console": "integratedTerminal",
            "justMyCode": true,
        }
    ]
}

This was throwing an error Error: No such option: --ppid I am trying to understand your thought process for arriving at the solution. How did you arrive at using module: "functions-framework" instead of the program field and Why does it work?

[chesedo]

@rahulbansal16 sorry for only seeing this now. I honestly have no idea how I arrived at module: "functions-framework" or why it works :joy:

I created this about 3 years ago, and have not needed to use it for about 2 and a half years.

Hmm, I might have wanted to connect the local debugger to this and figured that starting a python module gave the required flexibility :man_shrugging: