Ansible and FreeBSD don't agree who should decide the default python interpreter #29

Closed
opened 2022-07-01 08:15:50 -05:00 by crest · 0 comments
Owner

Ansible gained support for automatically picking a sane Python version a while ago, but FreeBSD has meta ports/packages for the default Python, Python 2.x and Python 3.x versions installing symlinks to the correct version for ages. While Ansible works just fine going through the FreeBSD symlink to the default Python version its own autodetection magic knows which path it should've autodetected. If the per group/host interpreter path doesn't match it writes an annoying warning on every invocation.

Ansible gained support for automatically picking a sane Python version a while ago, but FreeBSD has meta ports/packages for the default Python, Python 2.x and Python 3.x versions installing symlinks to the correct version for ages. While Ansible works just fine going through the FreeBSD symlink to the default Python version its own autodetection magic knows which path it should've autodetected. If the per group/host interpreter path doesn't match it writes an annoying warning on every invocation.
crest self-assigned this 2022-07-01 08:15:50 -05:00
crest closed this issue 2022-07-01 08:17:06 -05:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ccchb/ansible#29
No description provided.