- Mac 10.14.6
- PyCharm Community 2019.2
- python 2.7.10
- pip 19.2.2
- virtualenv 16.7.2
- Latest code from maintenance branch
Things used to work fine for months until I decided to test against OctoPrint 1.3.9 in my dev environment using existing installation. I checked out the corresponding tag, deleted venv folder and followed setup steps. Things worked fine and I was able to run my tests.
I then wanted to go back to latest and PyCharm came with a vengeance. I checked out maintenance again, deleted venv folder and followed normal setup steps. I can run OctoPrint from command line, I can run it from PyCharm (pressing green play icon) but I cannot debug it. I deleted the entire OctoPrint folder and did new clone steps, followed setup and nada.
It goes as far as:
2019-08-15 20:41:01,597 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin forcelogin
and then it exits with Process finished with exit code 1.
It seems like when it executes sarge.run(command + ["--version"], stdout=sarge.Capture(), stderr=sarge.Capture()) trying to find which pip is installed and which version that for some reason it exists. I tried debugging raised exceptions but couldn't figure out which one of the many raised is the one that matters (if any). I surrounded the #run() call with a try/except and I see that it prints an error like NoneType object is not callable.
I can go to the terminal in PyCharm and start up OctoPrint just fine. Running which pip returns:
which I think is ok. Running out of ideas how to be able to debug OctoPrint again. Of course I tried turning it off and on ... again and still nada.
Any suggestion or idea how to get this back running will be much appreciated.