Description of problem: $Summary. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
While installing python3 isn't a problem, getting that working for el7/el6 stuff that run inside a mock is going to be more challenging to impossible EL7 does not have appropriate amount of python3 support without using SCL or EPEL. So now we need to make a call on how we handle this.
At least CentOS 6 and 7 packages are expected to keep working fine with the standard Python (2) in the distribution. I am not sure of the requirement to move *everything* to Python3. Kaleb, could you be a little more specific and explain the need for it?
Kaleb is doing this correctly as per Fedora packaging guidelines (see https://fedoraproject.org/wiki/Packaging:Python). You cannot simply use python anymore. You have to specify python2 or python3 including in the shebang for all scripts. This is going to cause interesting problems for the EL6/EL7 world. The only way I can see this work is if we make sure we're compatible with python3 with tooling, but actually run all our stuff on python2 until such a time that there is an EL7 which ships python3 packages in base.