-
Notifications
You must be signed in to change notification settings - Fork 9
Configure debugpy python path for Windows/macOS environments #18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Thank you for the contribution💜 I tested it today on Windows and it worked perfectly. @lmotta any plans to merge it soon? |
|
works for me on windows |
|
It works for me on Windows 10 too. Love to see this merged so I don't have to manually patch the plugin after installation. |
|
I second this. This PR would be really helpful to have |
|
Confirmed that this fix worked for my needs on Darwin (Mac OSX) |
|
Hi @lmotta, (CC: @cvvergara) |
|
Hi @sanak, Thank you for your work on improving QGIS debugging workflows. I wanted to let you (and others watching this repository) know that we've recently released a new plugin called QGIS DevTools, which provides similar functionality with a focus on long-term maintainability and extensibility. QGIS DevTools supports debugging QGIS Python code via debugpy and Visual Studio Code, including features such as:
You can find more information here:
We warmly invite you and others interested in this topic to try it out and share feedback or contribute. |
|
Thank's @ivanbarsukov. Last week I worked on my plugin (the updates are on GitHub), with contributions from Ilan [1] and other fixes. I was going to update the plugin, but with your work, I'll mark mine as deprecated. I tested your plugin, and it's great. Take a look at the launch.json in my repository. In it, there's no need to define pathMappings or logging. We can use the debugger with more than one plugin. If possible, take advantage of the 'Load script' feature that's available in my repository. Being able to test a piece of code (script) before adding it to the plugin also helps |
|
Hi, @lmotta! Thank you so much for your kind words and support — it means a lot coming from the original author of We’ve just released QGIS DevTools 1.3.0, which now includes features based on your suggestions:
Thanks again for sharing your ideas. Best regards,
|
|
Thank you Ivan.
I am very pleased with your work in maintaining this tool, especially since
I personally met NextGIS, having been with Maxim at FOSS4G 2015.
Best regards,
Luiz Motta
OSGEO Brazil
Em sáb., 1 de nov. de 2025 às 17:04, Ivan Barsukov ***@***.***>
escreveu:
… *ivanbarsukov* left a comment (lmotta/debug_vs#18)
<#18 (comment)>
Hi, @lmotta <https://github.com/lmotta>!
Thank you so much for your kind words and support — it means a lot coming
from the original author of debug_vs.
We’ve just released QGIS DevTools 1.3.0
<https://github.com/nextgis/qgis_devtools/releases/tag/v1.3.0>, which now
includes features based on your suggestions:
- Script debugging support
- A simplified way to copy launch.json without needing to manually
specify pathMappings
Thanks again for sharing your ideas.
Best regards,
Ivan Barsukov
—
Reply to this email directly, view it on GitHub
<#18 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABPIFZ4VFGKJAJUU25EKTL32UG4LAVCNFSM6AAAAABG4GJNXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINZWG42TCOBXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Cheers, Luiz, good memories! Thanks for your support :) |

This is similar with PR #14, but using another approach to support both Windows/macOS environments.
I get python path from the following issue/PR and I just used 2nd PR's
get_qgis_python_pathfunction.This PR should solve all Windows/macOS related issues (#12, #13, #16, #17).
I still haven't tested this on Linux environment, but I will check it tomorrow.
=> 2024-04-29: I confirmed that Linux environment (Ubuntu 22.04 amd64, QGIS 3.34 LTS) works fine.