Closed salimfadhley closed 5 years ago
When you say "run the plugin", what do you mean, open the plugin window? or click the "Run" button in the plugin window? This is quite weird because the plugin doesn't need know the path to Python interpreter, only to mypy daemon. Maybe you can attach a screenshot?
Looking at the screenshots I got in an e-mail (I have no idea why the comment is not here anymore, was it deleted?) this is not our plugin.
Hey @ilevkivskyi, yep, I deleted it after I found out it was probably the wrong plugin. It is the one installed from the marketplace, not manually. After installing this one, I got it working by modifying the command used, to use Docker instead. Looks like it works.
@MrSaints having a similar issue: how did you "modify.. the command used"?
answered my own question: you right-click anywhere in the mypy terminal module and click "Configure plugin..." from the contextual dropdown
The plugin works fine if we use base system python or a virtual environment, however, if the Project's interpreter is running from Docker or a docker-compose configuration, the plugin doesn't seem to run.
I have a Python interpreter running from a Docker-Compose image. The image contains Python 3.6 and the MyPy library.
When you try to run the plugin you get a bubble:
If you click on "Configure Python Interpreter" it takes you to the Project Interpreter settings, however, there already is a Python interpreter for the project.