Python 3.6 update help

[EHRETic]

Hi there,

As you know, Netbox 3 will drop Python 3.6 support so I want to migrate to a newer version as soon as I can.

The thing is:

• I'm using CentOS 8 for the moment, planning to migrate "on the fly" to AlmaLinux, so I'll keep the RHEL8 family for a while.
• the default Python version on CentOS 8 is 3.6, I've no clue if this will change anytime soon and as I'm not a Linux pro, I installed the default
• I'd like to make this as clean as possible, so default would be let's say 3.9.X and I'd like to be updated automatically of course

Sound maybe stupid, but all article I could read would compile another Python aside the default version, but I don't know how this "works", so what will happen when default will be replaced, is the newly compiled version automatically updated, what happens if the new default is the one I've compiled, etc...

So anybody that can help and fill up the holes me is welcome! 😉
(And this guide might help a few others...)

[jeremystretch]

Sound maybe stupid, but all article I could read would compile another Python aside the default version, but I don't know how this "works", so what will happen when default will be replaced, is the newly compiled version automatically updated, what happens if the new default is the one I've compiled, etc...

The default Python installation is what the operating system uses natively, but you can install additional Python versions in parallel for use by individual applications. For example, I have 3.5 through 3.9 installed on my local system:

$ ls -l /usr/bin/python3.?
-rwxr-xr-x 2 root root 4117024 Feb 20  2021 /usr/bin/python3.5
-rwxr-xr-x 2 root root 4526456 Jan 26  2021 /usr/bin/python3.6
-rwxr-xr-x 2 root root 5308240 Feb 20  2021 /usr/bin/python3.7
-rwxr-xr-x 1 root root 5138128 Apr  2 21:00 /usr/bin/python3.8
-rwxr-xr-x 1 root root 5381008 Jul  3 13:50 /usr/bin/python3.9

The system's python3 alias will link to /usr/bin/python3.6, but you can run any of these independently.

For NetBox v3.0, you can specify your desired Python version when executing the upgrade script using an environment variable, like this:

PYTHON=/usr/bin/python/3.7 upgrade.sh

[baldgeek]

I have a centos 8 netbox install that I moved to python 3.8 when I upgraded to 2.11.11 without issue using these commands. This also moved the system default to python 3.8 dnf install python38 (verify what is installing is what you want) alternatives --config python3 (pick python3.8 from the list)

…

On 8/26/21 8:59 AM, Jeremy Stretch wrote: Sound maybe stupid, but all article I could read would compile another Python aside the default version, but I don't know how this "works", so what will happen when default will be replaced, is the newly compiled version automatically updated, what happens if the new default is the one I've compiled, etc... The /default/ Python installation is what the operating system uses natively, but you can install additional Python versions in parallel for use by individual applications. For example, I have 3.5 through 3.9 installed on my local system: |$ ls -l /usr/bin/python3.? -rwxr-xr-x 2 root root 4117024 Feb 20 2021 /usr/bin/python3.5 -rwxr-xr-x 2 root root 4526456 Jan 26 2021 /usr/bin/python3.6 -rwxr-xr-x 2 root root 5308240 Feb 20 2021 /usr/bin/python3.7 -rwxr-xr-x 1 root root 5138128 Apr 2 21:00 /usr/bin/python3.8 -rwxr-xr-x 1 root root 5381008 Jul 3 13:50 /usr/bin/python3.9 | The system's |python3| alias will link to |/usr/bin/python3.6|, but you can run any of these independently. For NetBox v3.0, you can specify your desired Python version when executing the upgrade script using an environment variable, like this: |PYTHON=/usr/bin/python/3.7 upgrade.sh | — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetbox-community%2Fnetbox%2Fdiscussions%2F7039%23discussioncomment-1239215&data=04%7C01%7Cjos100%40psu.edu%7C82b28e705f7b4ab292fa08d96891567c%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637655795693934751%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uRmUmgI6LXjoMqJC2M%2Bly2RibWvOzU77VuTbsrCc57o%3D&reserved=0>, or unsubscribe <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANYW3MNQBNEJUA7OR4NL5SLT6Y3C7ANCNFSM5C2ULJGQ&data=04%7C01%7Cjos100%40psu.edu%7C82b28e705f7b4ab292fa08d96891567c%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637655795693934751%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W1hO44lD0ZDwZe8uH3YiWquc6ynGsxiAXJQpH9p8bNE%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cjos100%40psu.edu%7C82b28e705f7b4ab292fa08d96891567c%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637655795693944694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1sB4TddoGijsdCTXckEm7yAoHzqJoTWKp%2FQXG%2BtFL1s%3D&reserved=0> or Android <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04%7C01%7Cjos100%40psu.edu%7C82b28e705f7b4ab292fa08d96891567c%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637655795693944694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6Vt4ijW9pplT47dPnUT5ftny59DPHXdDpU1100KJGEI%3D&reserved=0>.

[EHRETic]

@baldgeek @jeremystretch thanks a lot for both your advice! 😉

I did try the Python update alone but Netbox didn't run anymore right after the update+reboot so as I also had a snapshot of my VM (NB 2.11.11), I reverted it so I would be able to run the upgrade script to 2.11.12 once again after the updated Python (3.9) which is also now the new default.

Is that OK? (As I didn't know if I can run the same upgrade script twice)

[candlerb]

Certainly it is safe to run ./upgrade.sh multiple times. Each time it will just recreate the virtualenv and check if there are any database migrations to apply (and if there are none, then it won't do any).

[EHRETic]

Certainly it is safe to run ./upgrade.sh multiple times. Each time it will just recreate the virtualenv and check if there are any database migrations to apply (and if there are none, then it won't do any).

Good to know, thanks a lot and it seems I migrated Python at the right time as 3.0 is out!!! 😁