On Wed, Aug 14, 2019 at 4:31 PM Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > David Sommerseth wrote: > > Instead of spending time and resources keeping old stuff alive longer than > > needed, rather spend that energy on porting the old Python 2 over to > > Python 3. In the long run, this will result in far less work over time. > > It is not practical to get all the legacy Python 2 code ported over to > Python 3. Keeping Python 2 (or something backwards-compatible with it such > as Tauthon) available is actually the much more scalable approach. > > Your scorched earth approach will lose a lot of software that has no > replacement and that users rely on. I've been seeing migrations like this for d decades, with major releases of many software tools. Preserving legacy versions, forever, is the precise opposite of "scalable". _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
