You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rather than using virtualenv, we develop with a python env contained in a custom docker image.
I'm wondering if pyright can see into that built image to look for installed modules?
where the dockerfile looks something like this:
FROM python:3-stretch
RUN pip install --upgrade pip
ADD submodules/xyz/package /tmp/dpl
RUN cd /tmp/dpl && python setup.py sdist bdist_wheel
ENV PIP_FIND_LINKS=/tmp/dpl/dist
ADD requirements.txt ./
RUN pip install -r requirements.txt
The text was updated successfully, but these errors were encountered:
I believe it's common to use VS Code's remote mode (which makes dev containers work) to ensure the editor bits are running in the right environment. I'm not sure it's feasible to get the editor to use a container's filesystem without actually running in it.
Are you running Pyright (the command-line version) inside of the docker container? We run Pyright inside of a docker container for our CI (continuous integration) pipeline. Or are you looking to run the VS Code extension outside of the docker container but point to the docker container for your installed Python environment?
Pyright should be able to use any Python environment as long as it's accessible through a file system path.
rather than using virtualenv, we develop with a python env contained in a custom docker image.
I'm wondering if pyright can see into that built image to look for installed modules?
where the dockerfile looks something like this:
The text was updated successfully, but these errors were encountered: