On Tue, Apr 24, 2018 at 11:17:08PM +0000, Jeremy Stanley wrote: > On 2018-04-25 01:05:59 +0200 (+0200), Andrea Bolognani wrote: > [...] > > So you could say that RHEL is taking the approach described above - > > having a transitional period where both versions are available side > > by side - with the only difference being that Python 3 is currently > > not delivered through the same channel as Python 2. > > Given that "software collections" provides a containerized Python 3 > build and basically none of the rest of the Python ecosystem > modules outside the stdlib (which would all require manual > rebuilding against it), this is nowhere close to the same as > providing an optional Python interpreter within the global system > context as Debian has done. At least the projects I work on don't > see RHEL software collections Python 3 as remotely supportable. Fair enough; the point about distribution with lifecycles closer to Debian's keeping Python 2 around for a while after switching their default to Python 3 still stands. -- Andrea Bolognani <eof@kiyuko.org> Resistance is futile, you will be garbage collected.
Attachment:
signature.asc
Description: PGP signature