I'm not aware of any blogs documentation but the biggest reason is that Ansible relies on the fork syscall as part of the worker execution module. The Win32 layer has no concept of fork() and relies on threading to offer a similar alternative for multiprocessing in that world. As for why you can't use Python modules currently; the main module helper library used to parse the params and validate the input uses some Python libraries like pty which have no equivalent in Windows. TLDR; Ansible uses a lot of POSIX idioms which don't translate well to Windows.
If you are using Windows 10 I would highly recommend you use WSL and not Cygwin when running Ansible locally. It's not officially supported but I've yet to come across an issue with it and I think Microsoft has done an excellent implementation with that. WSL works because it handles all the POSIX syscalls for you (similar to Cygwin) but is also able to run unmodified ELF binaries (unlike Cygwin). Thanks Jordan -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9a66210c-09e6-422a-bfde-914874fd8090%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
