The reason why this occurs is because 2.4 introduce some recursive symbolic links to the test folder that ultimately causes the path is too long error message on Windows. This was fixed [1] and will be part of the 2.4.4 and 2.5.0 release, when testing the 2.5.0rc3 pip install it succeeds on a Windows Server 2016 box.
We have also added some checks to the CI [2] to verify the filenames are valid on Windows to try and avoid some of these issues from appearing in the future but if you come across any more issue pleases raise a Github request. In saying all this, while we do want to allow Ansible to be downloaded on a Windows host, this in no way means Ansible (as a controller) will work on Windows or any of the Python code will work properly. So you can install with pip and view the code, but when calling any of the code inside Ansible like ansible-lint does, it may still not work. [1] https://github.com/ansible/ansible/pull/35073 [2] https://github.com/ansible/ansible/blob/devel/test/sanity/code-smell/no-illegal-filenames.py 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/55cc0442-d922-4d5e-a8cb-b92e72a5b778%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
