Breakpoints are not hit in xlOil Python Debugging

[jxbean]

I have tried to set up debugging in VS Code and Visual Studio, but neither has been able to break at the breakpoint. Is there a more detailed tutorial on debugging? I saw some settings for debugging pyxll in PyCharm online and tried to set it up accordingly, but it didn't work.

[cunnane]

At one time it was possible to use Visual Studio to attach to a running Excel process, then open a py file containing an xlOil funcion, add breakpoints and they would be hit. Trying this now, it no longer seems to work. As a workaround, you can create an empty C++ project in Visual Studio, then in the debug settings chose C:\Program Files...\Excel.exe as the debug target and the "python/native" debugger:

When I launch Excel like this, I can hit breakpoints in xlOil py functions. It's not particularly convenient so I'll experiment with other options. Unfortunately I don't have PyCharm Pro, so can't test out its embedded python debugging.

[jxbean]

Thank you for the explanation. I’m unsure how to integrate the Python file with this empty C++ project. What should the complete project structure look like? How should I add my Python scripts properly and set breakpoints?

[keithalewis]

I don't know how to solve this issue, but you can use $(registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\excel.exe) as the Debugging Command to start Excel no matter where it was installed.

[cunnane]

You don't need to add anything to the project, it's just there to launch the app. You can open the files you want by navigating to them in the IDE's Open dialog, then click to add breakpoints as normal

…

On Mon, 12 Aug 2024, 07:14 jxbean, ***@***.***> wrote: Thank you for the explanation. I’m unsure how to integrate the Python file with this empty C++ project. What should the complete project structure look like? How should I add my Python scripts properly and set breakpoints? — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFOUG4DFQ7GLTHXTRSKY45LZRBABVAVCNFSM6AAAAABLA5Q4CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBTGEZDKOJUGM> . You are receiving this because you commented.Message ID: ***@***.***>

[jxbean]

Thanks again. It seems that there is a requirement for the python version, and 3.9 version is recommended and needs to install debugging symbols for Python interpreters in Visual Studio. It works for me now.

[cunnane]

Btw nice trick @keithalewis !

[jxbean]

Setting the 'launch.json' file with the 'Attach using Process Id' method as below in vscode works, and Python versions higher than 3.9 works fine.

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: Attach using Process Id",
            "type": "debugpy",
            "request": "attach",
            "processId": "${command:pickProcess}",
            "connect": {
                "host": "127.0.0.1",
                "port": 5678
            },
            "justMyCode": true,
            "pathMappings": [
                {
                    "localRoot": "${workspaceFolder}",
                    "remoteRoot": "${workspaceFolder}"
                }
            ]
        }
    ]
}