# Issue with Ansible on Rocky Linux 8.10 (Python 3.12) – "future feature annotations is not defined" **URL:** \ **Category:** Get Help\ **Tags:** centos, rockylinux\ **Created:** [March 19, 2025, 8:09am UTC](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117 "2025-03-19T08:09:31Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [April 21, 2025, 3:08pm UTC](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117/7 "2025-04-21T15:08:13Z")
You may want to check this response for more detailed information: > [@Python 3.7+ Impact on EL8 (future for EL9)](https://forum.ansible.com/t/python-3-7-impact-on-el8-future-for-el9/6229/13): > > I’ve held off on posting, largely because this is super complex problem. One we haven’t felt we’ve had a perfect solution for going on years now. This topic consumes an inordinate amount of engineering time continuously trying meet the needs of users, while simultaneously acknowledging our engineering limitations. Each year, or multiple times a year we think we’ve come to a concensus, and rinse and repeat. Hopefully with what we’ve learned and past things we’ve done, we continue to get better, b… However, the long story short is the response I provided above, with the exception that Red Hat customers get extended critical security support for ansible-core 2.14 and ansible-core 2.16. --- _[View the full topic](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117)._