We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?

Given that python3 was expected to be incompatible with python2, the usage of "python" was deprecated leaving your scripts to specify "python2" or "python3".

On an AIX 7.3, if you type "python3" you get nothing ?

We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?

Hi Jose! I think I inadvertently combined two questions into one post. My primary question is regarding the ramifications of having two disparate python3.9 packages on my AIX servers--one as a LPP (python3.9.base) included with AIX 7.3.1.2 and the other installed as an RPM (python3.9-3.9.18-1.ppc) requisite for cloud-init. Since I have NOT included /opt/freeware/bin in my PATH at all, the ONLY python3 that will ever be called from the CLI would be the AIX native LPP:

# ls -l /usr/bin/python3
lrwxrwxrwx    1 root     system           30 Oct 26 15:16 /usr/bin/python3 -> /usr/opt/python3/bin/python3.9

# ls -l /usr/opt/python3/bin/python3.9
-rwxr-xr-x    1 root     system       222119 Jun 21 05:33 /usr/opt/python3/bin/python3.9

# ls -l /opt/freeware/bin/python3.9
-rwxr-xr-x    1 root     system       189332 Sep 19 03:00 /opt/freeware/bin/python3.9

I suppose I could tack ":/opt/freeware/bin" to the end of my PATH, but so long as ":/usr/bin" has precedence in my PATH, it wouldn't change anything.

I think your response touched on another question that I have, namely whether there should also be a /usr/bin/python linked to /usr/opt/python3/bin/python3.9, as well as /usr/bin/python3. I think you have answered that question for me (i.e. "python", which is python2, is "deprecated" or "disallowed" or "unsupported" from this AIX release forward.).

Given that python3 was expected to be incompatible with python2, the usage of "python" was deprecated leaving your scripts to specify "python2" or "python3".

On an AIX 7.3, if you type "python3" you get nothing ?

We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?

Hi Jose! I think I inadvertently combined two questions into one post. My primary question is regarding the ramifications of having two disparate python3.9 packages on my AIX servers--one as a LPP (python3.9.base) included with AIX 7.3.1.2 and the other installed as an RPM (python3.9-3.9.18-1.ppc) requisite for cloud-init. Since I have NOT included /opt/freeware/bin in my PATH at all, the ONLY python3 that will ever be called from the CLI would be the AIX native LPP:

# ls -l /usr/bin/python3
lrwxrwxrwx    1 root     system           30 Oct 26 15:16 /usr/bin/python3 -> /usr/opt/python3/bin/python3.9

# ls -l /usr/opt/python3/bin/python3.9
-rwxr-xr-x    1 root     system       222119 Jun 21 05:33 /usr/opt/python3/bin/python3.9

# ls -l /opt/freeware/bin/python3.9
-rwxr-xr-x    1 root     system       189332 Sep 19 03:00 /opt/freeware/bin/python3.9

I suppose I could tack ":/opt/freeware/bin" to the end of my PATH, but so long as ":/usr/bin" has precedence in my PATH, it wouldn't change anything.

I think your response touched on another question that I have, namely whether there should also be a /usr/bin/python linked to /usr/opt/python3/bin/python3.9, as well as /usr/bin/python3. I think you have answered that question for me (i.e. "python", which is python2, is "deprecated" or "disallowed" or "unsupported" from this AIX release forward.).

Given that python3 was expected to be incompatible with python2, the usage of "python" was deprecated leaving your scripts to specify "python2" or "python3".

On an AIX 7.3, if you type "python3" you get nothing ?

We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?

Hi Jose! I think I inadvertently combined two questions into one post. My primary question is regarding the ramifications of having two disparate python3.9 packages on my AIX servers--one as a LPP (python3.9.base) included with AIX 7.3.1.2 and the other installed as an RPM (python3.9-3.9.18-1.ppc) requisite for cloud-init. Since I have NOT included /opt/freeware/bin in my PATH at all, the ONLY python3 that will ever be called from the CLI would be the AIX native LPP:

# ls -l /usr/bin/python3
lrwxrwxrwx    1 root     system           30 Oct 26 15:16 /usr/bin/python3 -> /usr/opt/python3/bin/python3.9

# ls -l /usr/opt/python3/bin/python3.9
-rwxr-xr-x    1 root     system       222119 Jun 21 05:33 /usr/opt/python3/bin/python3.9

# ls -l /opt/freeware/bin/python3.9
-rwxr-xr-x    1 root     system       189332 Sep 19 03:00 /opt/freeware/bin/python3.9

I suppose I could tack ":/opt/freeware/bin" to the end of my PATH, but so long as ":/usr/bin" has precedence in my PATH, it wouldn't change anything.

I think your response touched on another question that I have, namely whether there should also be a /usr/bin/python linked to /usr/opt/python3/bin/python3.9, as well as /usr/bin/python3. I think you have answered that question for me (i.e. "python", which is python2, is "deprecated" or "disallowed" or "unsupported" from this AIX release forward.).

Given that python3 was expected to be incompatible with python2, the usage of "python" was deprecated leaving your scripts to specify "python2" or "python3".

On an AIX 7.3, if you type "python3" you get nothing ?

We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?

BTW, if you have "funny" results, on 22.1, this file will invoke the default python3 instead of the opt freeware one.

/opt/freeware/lib/python3.9/site-packages/cloudinit/net/networkd.py:#!/usr/bin/env python3

Hi Jose! I think I inadvertently combined two questions into one post. My primary question is regarding the ramifications of having two disparate python3.9 packages on my AIX servers--one as a LPP (python3.9.base) included with AIX 7.3.1.2 and the other installed as an RPM (python3.9-3.9.18-1.ppc) requisite for cloud-init. Since I have NOT included /opt/freeware/bin in my PATH at all, the ONLY python3 that will ever be called from the CLI would be the AIX native LPP:

# ls -l /usr/bin/python3
lrwxrwxrwx    1 root     system           30 Oct 26 15:16 /usr/bin/python3 -> /usr/opt/python3/bin/python3.9

# ls -l /usr/opt/python3/bin/python3.9
-rwxr-xr-x    1 root     system       222119 Jun 21 05:33 /usr/opt/python3/bin/python3.9

# ls -l /opt/freeware/bin/python3.9
-rwxr-xr-x    1 root     system       189332 Sep 19 03:00 /opt/freeware/bin/python3.9

I suppose I could tack ":/opt/freeware/bin" to the end of my PATH, but so long as ":/usr/bin" has precedence in my PATH, it wouldn't change anything.

I think your response touched on another question that I have, namely whether there should also be a /usr/bin/python linked to /usr/opt/python3/bin/python3.9, as well as /usr/bin/python3. I think you have answered that question for me (i.e. "python", which is python2, is "deprecated" or "disallowed" or "unsupported" from this AIX release forward.).

Given that python3 was expected to be incompatible with python2, the usage of "python" was deprecated leaving your scripts to specify "python2" or "python3".

On an AIX 7.3, if you type "python3" you get nothing ?

We currently have two main requirements for python on AIX: 1) cloud-init (for PowerVC deployments) and 2) Ansible automation. We are having a difficult time getting our Automation Team to specify exactly which version/libraries of python they require/support for Ansible automation. In the mean time, I have been testing cloud-init-22.1-5.noarch with it's own RPM requisite python3.9-3.9.18-1.ppc. Now python3.9 is also included with AIX 7.3.1.2 as a LPP: python3.9.base 3.9.12.0. (BTW, in our post customization, we update this package to 3.9.18, I believe) But neither seem to be configured as the AIX "default" for "python" in our default PATH, at all. AIX 7.3.1.2 seems to be configured by "default" to have "python3" point to the LPP package in our PATH. So is the "python" executable considered to be deprecated now? Is there any reason that I should have/maintain two different python3.9 packages in AIX 7.3.1.2?