Is Ansible part of Python?

Ansible is not part of Python and isn't a Python library. It's a separate, independently maintained automation tool that happens to be built in Python: as of ansible-core 2.18, running the command line on a control node requires Python 3.11 or newer, though the servers it manages can often get by with an older Python 3.8 install.

How much Python does Ansible actually need?

The core runtime ships as its own installable package on PyPI, ansible-core, and the broader "ansible" package most people install pulls that runtime plus a curated set of community collections on top of it. The two packages even use different version numbers: Ansible 11, for instance, ships with ansible-core 2.18 underneath it, which confuses plenty of people the first time they run "ansible --version". The control node running the playbooks needs that current Python interpreter, while the managed servers being configured usually get by with whatever Python already ships on the OS, since Ansible executes small Python snippets over SSH rather than keeping a permanent agent installed.

Are Ansible's modules always written in Python?

Most of the thousands of built-in modules are Python scripts, which is a big part of why the project feels like a Python codebase from the inside and why Python developers tend to pick it up quickly. Ansible's module interface doesn't actually require Python, though: it accepts any module capable of reading JSON input and writing JSON output, so teams occasionally write custom modules in Bash, Go, or another language when that fits their environment better. A handful of built-in modules, like raw and script, are designed to work even on remote machines with no Python installed at all, which is part of how Ansible manages network switches and appliances that were never going to run a Python interpreter.

Updated: August 12, 2026