On Thu, Feb 2, 2023 at 7:56 AM Mike Eggleston <[email protected]> wrote: > > I built the most current (at the time) Python and installed the Python > executable in my home directory, then I used an Ansible variable in my > inventory file (I don’t remember which variable) to specify an alternate > Python interpreter and things were fine when I had an old Python interpreter > on a remote system. > > Mike
Until they're not. Provenance, compatibility, and consistency of python modules in different python builds can depend on a lot of factors, such as previously installed components detected at build time and regressions in updated components. It works until it doesn't, and the fix may be neither obvious, simple, nor local. It's why I'm such a strong advocate of packaging ansible tools rather than doing "pip install" with gods only know what the base python version might be and what is in pypi.org at this moment. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAOCN9rz%3DK8xuU_4%2B7MNEiQSoSB6cKDK5Ldnh2F0oG9gmwdm8zA%40mail.gmail.com.
