if you run the default shell in that flake, you will see the maturin error I'm talking about:

error: builder for '/nix/store/6bmn75r0iwlwwidng0am3s6qdgmh0jqk-python3.11-safetensors-0.4.2.drv' failed with exit code 2;
       last 10 log lines:
       >           ^^^^^^^^^^^^^^^^^^^^^^^
       >   File "/nix/store/sxr2igfkwhxbagri49b8krmcqz168sim-python3-3.11.8/lib/python3.11/importlib/__init__.py", line 126, in import_module
       >     return _bootstrap._gcd_import(name[level:], package, level)
       >            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       >   File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
       >   File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
       >   File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked
       > ModuleNotFoundError: No module named 'maturin'
       > 
       > 
       For full logs, run 'nix log /nix/store/6bmn75r0iwlwwidng0am3s6qdgmh0jqk-python3.11-safetensors-0.4.2.drv'.
error: 1 dependencies of derivation '/nix/store/z3yjz5pcr2j0fghlk78vngxl3bc16sda-python3-3.11.8-env.drv' failed to build
error: 1 dependencies of derivation '/nix/store/j2hn0kja87dqkw8043l7m56wjh0ny9yz-nix-shell-env.drv' failed to build

I solved the problem about maturin (and am writing this response in case someone has my problem). In the edgecases.md document it was advised to use preferWheel and preferWheels, but I wasn't aware of this:

https://github.com/nix-community/poetry2nix/issues/1115#issuecomment-1611913900
One should prefer:

overrides = poetry2nix.overrides.withDefaults (<...>);

to:

overrides = poetry2nix.defaultPoetryOverrides.extend (<...>);

otherwise, preferWheel = true is not respected.

Now I have still a problem, and I'm wandering if someone encountered it before:

RuntimeError: Cannot find CUDA_HOME. CUDA must be available to build the package.

This happens when I try to build the wheel for the last package I need, llvm itself. As usual, one can try the failing build at the latest commit of the repo I linked in the first question. I wonder who should set CUDA_HOME, and how could I set it so that the build process of vllm sees it (I don't think a shellHook is early enough)

Now I have still a problem, and I'm wondering if someone encountered it before:

RuntimeError: Cannot find CUDA_HOME. CUDA must be available to build the package.

This happens when I try to build the wheel for the last package I need, llvm itself. As usual, one can try the failing build at the latest commit of the repo I linked in the first question. I wonder who should set CUDA_HOME, and how could I set it so that the build process of vllm sees it (I don't think a shellHook is early enough)

Now I have still a problem, and I'm wondering if someone encountered it before:

RuntimeError: Cannot find CUDA_HOME. CUDA must be available to build the package.

This happens when I try to build the wheel for the last package I need, vllm itself. As usual, one can try the failing build at the latest commit of the repo I linked in the first question. I wonder who should set CUDA_HOME, and how could I set it so that the build process of vllm sees it (I don't think a shellHook is early enough)

Now I have still a problem, and I'm wondering if someone encountered it before:

RuntimeError: Cannot find CUDA_HOME. CUDA must be available to build the package.

This happens when I try to build the wheel for the last package I need, vllm itself. As usual, one can try the failing build at the latest commit of the repo I linked in the first question. I wonder who should set CUDA_HOME, and how could I set it so that the build process of vllm sees it (I don't think a shellHook is early enough)

I solved this problem via:

  addCudaHome = { name, final, prev, pkg }@args:
    pkg.overridePythonAttrs (old: {
      preBuild = (old.preBuild or "")
        + ''export CUDA_HOME="${final.pkgs.cudatoolkit}"'';
    });