Feature Suggestion: add python interpreter args to launch configuration

[DonJayamanne]

From @bsphere on January 29, 2017 22:6

This is very useful for debugging pyspark programs and adds the ability to add spark-submit args such as "--packages" and "--master"

Copied from original issue: DonJayamanne/pythonVSCode#682

[DonJayamanne]

You can add custom arguments to the python interpreter when debugging as follows:

• https://github.com/DonJayamanne/pythonVSCode/wiki/Debugging/_edit#args

{
    "name": "Python",
    "type": "python",
    "request": "launch",
    "stopOnEntry": true,
    "pythonPath": "config.python.pythonPath",
    "args": [
        "--packages", 
        "--master"
    ],
    "program": "file",
    "cwd": "workspaceRoot",
    "debugOptions": [
        "WaitOnAbnormalExit",
        "WaitOnNormalExit",
        "RedirectOutput"
    ]
},

[DonJayamanne]

From @bsphere on February 2, 2017 11:36

@DonJayamanne those are args to the python program and not for the python interpreter,
e.g. spark-submit --packages ....jar --conf spark.something.something=something program.py arg1

[mcdevitts]

Would adding this ability also allow for keeping the console open after the file / program has been run through the "-i" option? Having the ability whether in the debugger or in the "Run Python File in Terminal" option to keep the terminal open for inspection would be really handy.

[ali-alidoust]

I needed to add -X:PrivateBinding arg to IronPython interpreter,but as a temporary workaround I created a batch/shell script like the following and added the arg there:

 @echo off
 "C:\Program Files\IronPython 2.7\ipy.exe" -X:PrivateBinding %*

then in the launch.json file I set pythonPath variable to my batch file:

{
  ...
  "pythonPath": "${workspaceFolder}/ipy.bat",
  ...
}

[brettcannon]

To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.