# Ansible supported Python version on \_target\_

**URL:** <https://forum.ansible.com/t/ansible-supported-python-version-on-target/44863>\
**Category:** Project Discussions\
**Tags:** ansible, linux, ansible-core\
**Created:** [November 19, 2025, 3:31pm UTC](https://forum.ansible.com/t/ansible-supported-python-version-on-target/44863 "2025-11-19T15:31:23Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Thulium-Drake](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/thulium-drake/32/833_2.png) [@Thulium-Drake](https://forum.ansible.com/u/Thulium-Drake)\
**Post date:** [February 5, 2026, 12:52pm UTC](https://forum.ansible.com/t/ansible-supported-python-version-on-target/44863/15 "2026-02-05T12:52:47Z")

</div>

So after having a very interesting few chats with @nitzmahone (thanks for those btw 🙂 I appreciate it and it was nice meeting you!) it seems I, the instigator of this latest dust-up, need to dole out some props where they are due!

@sivel and the others involved: Thanks for your work on [Support core packaging operations against older python versions by sivel · Pull Request #86432 · ansible/ansible · GitHub](https://github.com/ansible/ansible/pull/86432). If this comes to fruition in a next version of Ansible, it might just be the fix we’ve been looking for (from the sound of it I know I am) to de-couple the target’s Python version from what Ansible needs.

🚀

---

_[View the full topic](https://forum.ansible.com/t/ansible-supported-python-version-on-target/44863)._
