Update Pyramid debug template to use `python -m pyramid.scripts.pserve`

[JDeuce]

Hi there has been an issue reported before where the "Pyramid" debug option tries to find the wrong pserve on some platforms.

#530

The fix was submitted here:

f22b451

And it added this block of code to fix it, which uses pserve.exe on Windows and pserve on everything else:
https://github.com/jpfarias/vscode-python/blob/master/src/client/debugger/Main.ts#L217-L224

I don't believe this fix was sufficient as today using VSCode 1.26.1 and vscode-python 2018.7.1 I was getting launch error Unable to locate 'pserve.py' required for debugging Pyramid application

Solution for me was to just not try to use the "program" launch style, but instead use the "module" launch style like the "flask" example. I think you guys should consider changing the default to this as it is simpler to understand ..... and deprecate the custom DebugOption as it is not required nor simpler:

    {
            "name": "Python: Pyramid",
            "type": "python",
            "request": "launch",
            "module": "pyramid.scripts.pserve",
            "args": [
                "${workspaceFolder}/development.ini"
            ],
            "debugOptions": [
                "RedirectOutput",
            ]
        }

[brettcannon]

So our current solution works for me, but your idea does seem reasonable, @JDeuce . I have asked on Twitter whether we can rely on this since none of the Pyramid docs seem to suggest this is a supported way to start up pserve.

[JDeuce]

Ok,
I can refer to the git blame on setup.py for pyramid which shows that the pserve command has been pserve.scripts.main for at least 7 years:
https://github.com/Pylons/pyramid/blame/master/setup.py#L105
when it appears to have been added in the initial commit for pserve
Pylons/pyramid@0e0cb76
I guess if it's not documented they could decide to change it.

I investigated a little more on my system. This is the error I was getting.

I had the pythonPath set to the same virtualenv "${workspaceFolder/env}" in both in launch.json and expected it to work. I played with it a bit more and ended up getting the error to go away when I set

"python.pythonPath": "${workspaceFolder}/env/Scripts/python.exe"

in my workspace settings. So I think it has to do with the setup.py console script wrapper (pserve.exe) starting a new interpreter that uses the other path or something, which is an interesting distinction from the other module style launch option.

[stevepiercy]

none of the Pyramid docs seem to suggest this is a supported way to start up pserve.

@brettcannon I'm not sure whether these two Pyramid docs cover what you did not find. If not, please let me know how to improve them. I'd be happy to update them. Thank you!

• pserve command documentation
• Running the Project Application