Closed djkmiles closed 6 years ago
Sorry it took so long to reply. Didn't see the pull request.
There's really no need to have to know the location if python was added to path and where python
or the respective command works. What I was confused about is whether which python
works on mac and returns the correct version, since from what I understand, python 2 comes pre-installed, so what happens when you install 3 on top of that? Would which python
point to 2 or 3? Same thing with linux if python is installed.
BUT since it's not really python itself the add-on uses, just the ptvsd package, I just tested installing ptvsd with python 2 and there seems to be no problems not using the correct Python version since it's compatible with both. I'm not that familiar with python so I'm not sure how all that is handled, but it works. So that means regardless of which python the add-on finds, it will be the one available to the command line and therefore the one used by pip to install ptvsd, so there should be no problems. Edit: Except on the VS Code side, that does need to detect the right Python for intellisense to work correctly. I will update the documentation later with all this.
Have you tested the add-on on a mac, does it auto-find the path and work? If so I'll just remove the part about it not being tested.
I'm trying to setup VSCode debug on Blender for Os X. I have pyenv (virtual environment for python) installed and I can tell you which works correctly. I have tested with default Os X python sometimes ago and I remember it worked. Until now anyway I had no luck, debugger seems to ignore my setup. In the following days I'll try with your addon.
@kabukunz As I mentioned in the edit on the previous comment it turns out the python version only seems to matter for VS Code (for the intellisense). I will update the documentation in a sec and close this. If you have any issues setting things up just file a new issue.
Add PTVSD location for macOS users