# \`ansible-playbook\` (\`ansible-core 2.17.1\`) fails on target with \`python 3.9\`

**URL:** <https://forum.ansible.com/t/ansible-playbook-ansible-core-2-17-1-fails-on-target-with-python-3-9/6700>\
**Category:** Get Help\
**Tags:** python, ansible-core\
**Created:** [June 21, 2024, 7:44am UTC](https://forum.ansible.com/t/ansible-playbook-ansible-core-2-17-1-fails-on-target-with-python-3-9/6700 "2024-06-21T07:44:25Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [July 11, 2024, 7:19pm UTC](https://forum.ansible.com/t/ansible-playbook-ansible-core-2-17-1-fails-on-target-with-python-3-9/6700/12 "2024-07-11T19:19:54Z")

</div>

I created an experiment:

I copied all module\_utils (except C#/PowerShell; and six, since the collection loader will barf if that’s around somewhere outside ansible.builtin…), doc fragments, and the action plugins/modules related to package modules that do respawning (i.e. apt, apt\_repository, dnf, yum) from stable-2.16 to a collection and adjusted the imports, and some more smaller changes (mostly related to how arguments are passed to Python Ansible modules, and new hidden `_ansible_*` parameters added in ansible-core 2.17).

That way, I hope that respawn also works with Python 2.7 and 3.6, since there should be no syntax errors coming from module utils.

Can someone try [GitHub - felixfontein/ansible-py2736compattest](https://github.com/felixfontein/ansible-py2736compattest) (the collection is called felixfontein.py2736compattest) to see whether it works as I hope?

---

_[View the full topic](https://forum.ansible.com/t/ansible-playbook-ansible-core-2-17-1-fails-on-target-with-python-3-9/6700)._