# \[ansible/ansible\] Add /opt/bin/python to python fallback list (PR #82821) **URL:** \ **Category:** Ansible Developer\ **Created:** [March 14, 2024, 10:50pm UTC](https://forum.ansible.com/t/ansible-ansible-add-opt-bin-python-to-python-fallback-list-pr-82821/38717 "2024-03-14T22:50:33Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![VannTen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/vannten/32/9911_2.png) [@VannTen](https://forum.ansible.com/u/VannTen)\ **Post date:** [March 14, 2024, 10:50pm UTC](https://forum.ansible.com/t/ansible-ansible-add-opt-bin-python-to-python-fallback-list-pr-82821/38717/1 "2024-03-14T22:50:33Z")
> \* 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](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](https://github.com/ansible/ansible/pull/82821)