>* You can configure this option yourself using the variable >`ansible_interpreter_python_fallback` so it's not something we plan on adding >to the defaults >
I know about that. Unfortunately, when developing a playbooks which itself has users (kubespray, as mentioned above), we're trying to preserve the possibility for users to themselves override variables, and group_vars is pretty low on the precedence list [1], so pretty much everything we'll do at the playbook role level will prevent users to set the variable in a fine grained manner (extra vars works, but it does not have hosts granularity). I'd would use role defaults, but I can't just add to the default value then, I have to replace it (since it's lazy it does not handle self reference, right ?) [1] : https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#id42 >Because this project is very active, we're unlikely to see comments made on >closed tickets and we lock them after some time. Cc'ing the ansible-devel list then. (Not sure why that's more visible. Link to the PR for list readers : https://github.com/ansible/ansible/pull/82821 -- Max Gautier -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/186203E3-B237-4B6C-A6B1-C57DC92D9C60%40max.gautier.name.
