Windows compatibility issues with installation and embedding pipeline

Open
#21 0 comments 0 reactions 1 assignee View on GitHub

@NetZissou is already working on this.

Since Mar 25, 2026.

Assessment

This issue has not been assessed yet.

Description

bug dependencies documentation enhancement

Windows compatibility issues with installation and embedding pipeline

Summary

Several issues prevent a smooth experience on Windows. Tested on Windows 11 with Python 3.12, CUDA 12.8 (Quadro P2000).

Issues

1. DataLoader crash: unpicklable lambda in ImageFolderDataset

Windows uses spawn (not fork) for multiprocessing. ImageFolderDataset._init_uuid_generator() assigns lambdas to self.generate_uuid, which cannot be pickled when num_workers > 0.

AttributeError: Can't get local object 'ImageFolderDataset._init_uuid_generator.<locals>.<lambda>'

Fix: Set num_workers=0 on Windows in embedding_service.py, or replace the lambdas in hpc-inference with a regular method.

2. gpu-cu12 / gpu-cu13 extras fail on Windows

cuML (RAPIDS) only ships Linux wheels. uv pip install -e ".[gpu-cu12]" fails with RuntimeError: Didn't find wheel for cuml-cu12.

Fix: Document that GPU extras (cuML) are Linux-only. Embedding still uses CUDA via PyTorch on Windows.

3. PyTorch installs as CPU-only by default

uv pip install -e . pulls the CPU-only torch from PyPI on Windows. Users must manually reinstall from PyTorch's CUDA index:

uv pip install torch torchvision --index-url https://download.pytorch.org/whl/cu124

Fix: Add Windows-specific CUDA PyTorch install instructions to README.

4. Missing pynvml dependency

Embedding fails at runtime with No module named 'pynvml'.

Fix: Add pynvml or nvidia-ml-py to project dependencies.

5. README venv activation command is Linux-only

source .venv/bin/activate does not exist on Windows. The correct path is .venv\Scripts\activate.

Fix: Add Windows activation instructions to README.

Dominant language
Python
Stars
8
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Imageomics/emb-explorer

All issues in Imageomics/emb-explorer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.