Fix setup

[sanzoghenzo]

This will hopefully fix the installation issue reported in #125.

The remote debugger was enabled, I added an environment variable to avoid rogue commits (and updated the readme accordingly).

I also took the liberty to make things more pythonic (mostly PEP8 naming style) and make the setup code DRY.

[sanzoghenzo]

Sorry, I see only now that you don't support the linux platform.

The PR solves the installation/activation problem, but I only tested on linux and then I got stuck because no accounts can be detected (no manager to read the info from).

EDIT: I followed the documentation on how to add an account manually and it works, so I guess linux can be added to the supported platforms along with a link to the documentation to add the accounts

[KatKatKateryna]

Hi @sanzoghenzo ! Glad it worked in the end.
Thanks for the contribution! There are some changes already piled up, I will take a look at PR right after they are merged, this or next week. Would you mind sharing which method you followed to make the accounts work on linux?

[sanzoghenzo]

Sorry, I thought I posted it already, it may be lost in my many edits 😅

Here it is

[KatKatKateryna]

Hi @sanzoghenzo ! The extra "bin" is necessary for Mac, as the executable path is not detected correctly (like reported, for example, here).

Could you please create another PR with only one check for mac/linux os in the existing get_qgis_python_path function, without any extra restructuring? Then I can merge it immediately and release this week with a new version. Remote debugging and dependencies are currently undergoing changes too.

Thanks!

[sanzoghenzo]

Hi, I hope it's OK that I just force-pushed the branch of this PR with what you asked.

I'm looking forward to see the new changes you have in store!

[KatKatKateryna]

Awesome, thanks!
More details on the same issue for the reference: qgis/QGIS#45646