Building package in a path with space characters fails on Windows

[sapetnioc]

I do not know if it is specific to Windows. I had the problem with libminc. It might be either a bug in rattler-build or a problem in escaping command parameters when calling rattler-build from Python.

[nsouedet]

The problem is probably around these lines :
https://github.com/neurospin/neuro-forge/blob/89dc17362c56c53eddac0b3cd91aaaa1ce143230/neuro_forge/soma_forge/commands/apply_plan.py#L85C1-L103C39

I think that it is a problem with rattler-build command call. Maybe this could help

[sapetnioc]

I am still hoping that it is not a problem here because I have no special character, just a space in C:\Users\FirstName LastName, and I believe it it the job of subprocess to correctly escape the command. But I will try another example with python instead of rattler-build to find out who is messing with my command.

[sapetnioc]

I believe the problem comes from rattler-build and is Windows specific because the following command fail (in PowerShell):

 rattler-build.exe build -r 'C:\Users\Me Myself\dev\neuro-forge\recipes\libminc' --output-dir 'C:\Users\Me Myself\dev\output'

But the following is working:

rattler-build.exe build -r 'C:\Users\Me Myself\dev\neuro-forge\recipes\libminc' --output-dir 'C:\Users\me\dev\output'

To activate the environment, rattler-build generates a script and use call on it without appropriate escaping:

 │ ╭─ Running build script
 │ │ %SRC_DIR%>IF "" == "" (
 │ │ 'C:\Users\Me' n’est pas reconnu en tant que commande interne
 │ │ ou externe, un programme exécutable ou un fichier de commandes.
 │ │
 │ │  call %SRC_DIR%\build_env.bat
 │ │ )