Earlier quoted context omitted.
Presumably with RHEL being around for 18 years users would be able to run "yum search python", see the packages are versioned, and yum install the version they want. All sans blog article. It's far from the first time in 18 years a package name has changed with a major version upgrade.
RedHat(IBM) employee?
What, No Python in RHEL 8 Beta?
61–63 of 63 posts
Re: What, No Python in RHEL 8 Beta?
#62Earlier quoted context omitted.
Note: You shouldn't use #!/usr/bin/env python. Instead you should explicitly specify python2 or python3, unless your script is compatible with both.
Totally agree in principle. One interesting note - MacOS doesn't have a /usr/bin/python2 (at least, not at the time of this writing). It supplies /usr/bin/python, and also /usr/bin/python2.7. That might not matter at all, but it's worth noting.
Re: What, No Python in RHEL 8 Beta?
#63Earlier quoted context omitted.
Yes, you're absolutely right about requirements.txt. However as you say, it's a problem when you have to start considering transitive dependencies. In fact, for the case I mentioned, this became a problem because there were so many it became increasingly complex; you ended up having to start moving more and more of the transitive dependencies directly into the requirements file. And this isn't very scalable. That on…
Transitive dependencies (or what I called inherited from other packages) can be solved with pip freeze in existing working environment; it will list them too. New development, on the other hand, will be difficult. As it usually is, when you develop in something that has been obsoleted years ago. If you are still developing the system, instead of just keeping it running, shouldn't you spend some resources on python3 m…
The times we have had to update things have been when the existing modules broke. One example which comes to mind from the recent past is when urllib TLS certificate stuff broke and it needed updating. In that case, it didn't cause collateral damage, but we were forced to do it to keep things working. Externally-enforced changes like this could potentially cause breakage in the future if they drop python 2.7 support directly or indirectly.