# Remote Execution Node and Python 3.11+

**URL:** <https://forum.ansible.com/t/remote-execution-node-and-python-3-11/44338>\
**Category:** Get Help\
**Created:** [August 21, 2025, 9:11am UTC](https://forum.ansible.com/t/remote-execution-node-and-python-3-11/44338 "2025-08-21T09:11:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ildjarn](https://avatars.discourse-cdn.com/v4/letter/i/8491ac/32.png) [@ildjarn](https://forum.ansible.com/u/ildjarn)\
**Post date:** [August 21, 2025, 9:11am UTC](https://forum.ansible.com/t/remote-execution-node-and-python-3-11/44338/1 "2025-08-21T09:11:27Z")

</div>

Python 3.11 introduced Externally Managed Python environments, and best practice is to use a venv.

The installer bundle for a remote execution node does not contain logic for this, as far as I know, and running the installer script stops while adding pip packages, with an `error: externally-managed-environment` error.

- Are there plans to introduce compatibility with an externally managed Python environment for the installer bundle?
- If not: Usually it’s a Very Bad Idea ™ to remove the EXTERNALLY-MANAGED file, but if the REN code is the only thing that will be installed on the node, how bad will this break things like system updates?