Not sure why you have it in the first place. Could you share a screenshot of your run configuration and another one showing this option when running tests?
Sergey Karpov Why is `--no-deps` enabled by default in the first place and why can't we remove it? Isn't the whole point of using a docker-compose run/debug config to automatically spin-up and tear-down a _group_ of containers in unison? If I didn't want any other containers running at the same time then I would just use a docker run config not docker-compose.
Hi,
PyCharm, in fact, doesn't support this option at the moment https://youtrack.jetbrains.com/issue/PY-37647
Not sure why you have it in the first place. Could you share a screenshot of your run configuration and another one showing this option when running tests?
Hi Sergey,
Thanks for your fast answer....
This is my config:
And YES, the idea is NOT USES the --no-deps when uses docker-compose run
The option PyCharm put this one automatic (see the screenshoot):
Thanks a lot,
Oh, I see, it is added automatically if you add run command to your run configuration. So I guess the workaround is to not use run.
Hi Sergey,
The detailt is I need use the run option because I need the containers create and destroy when the test are finished.
Sergey Karpov Why is `--no-deps` enabled by default in the first place and why can't we remove it? Isn't the whole point of using a docker-compose run/debug config to automatically spin-up and tear-down a _group_ of containers in unison? If I didn't want any other containers running at the same time then I would just use a docker run config not docker-compose.