ModuleNotFoundError: No module named 'deeptutor'

[grester]

In a windows server I'm having trouble running the Tour.
So I tried going with option B, I did so far:

1. python -m venv .venv && .venv\Scripts\activate
2. pip install -e ".[server]"
3. cd web && npm install && cd ..

However running the tour I'm getting the error: ModuleNotFoundError: No module named 'deeptutor'
Looking inside of .venv/lib and .venv/includes they are pretty much empty, so I have the sense the workspace folder that was supposed to auto include some deeptutor libs, in the tour script:

PROJECT_ROOT = Path(__file__).resolve().parent.parent
if str(PROJECT_ROOT) not in sys.path:
    sys.path.insert(0, str(PROJECT_ROOT))

or the def _python_strategy() isn't working as intended to find the necessary lib files despite the .venv being active.

So I'm a bit at a loss of what's working different on my envinronment that needs to be workaround.
Any tips?

[darekwojciechowski]

The clue is that .venv looks "pretty much empty" — that means pip install -e didn't actually install into this venv, so it's not a sys.path issue in the script, the package genuinely isn't there.

Two things go wrong on Windows here:

1. You're looking in the wrong folder. On Windows a venv puts packages in .venv\Lib\site-packages (capital L, "Lib" not "lib"), and scripts in .venv\Scripts. If you checked .venv/lib and .venv/includes you were looking at the Unix-style paths, which stay empty on Windows.

2. The venv probably wasn't actually active when pip ran, so the editable install went somewhere else (or failed). PowerShell blocks .venv\Scripts\Activate.ps1 by default via its execution policy, and activation can fail silently.

Do this to confirm and fix, using the venv's own Python explicitly so there's no ambiguity:

.venv\Scripts\python.exe -c "import sys; print(sys.prefix)"
should print your project's .venv path, not a global Python

.venv\Scripts\python.exe -m pip install -e ".[server]"
.venv\Scripts\python.exe -m pip show deeptutor
should now list the package with a Location pointing at your repo

Calling .venv\Scripts\python.exe -m pip ... guarantees the install lands in this venv regardless of whether activation "took". After that, run the tour with the same interpreter:

.venv\Scripts\python.exe path\to\tour_script.py

If pip show still doesn't find it, scroll up in the install output — an editable install that errored on a build step will leave you with exactly this ModuleNotFoundError.