View Single Post
Old 10-03-2020, 07:08 PM   #1096
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,343
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Uncle Robin View Post
But the Calibre update was all about fixing something that is at the very least about to be "broke", no? Migrating from Python 2 to 3 now seems like a good idea, rather than waiting for the obsolescence to set in.
Considering that development was started on Python 3 in 2006 and in 2008, it was announced that Jan. 01, 2015 was the EOL for Python 2? Due to complaints, that was extended to Jan. 01, 2020. It is now past the sunset date and yes, it's long past time to move on. In April, 2020, Python 2.7.18 was released which bundled the last fixes to 2.7.17 and that was it for any updates. Your nuclear power station is going to explode? Update the software to Python 3 instead of spending time working around the limitations of Python 2.
DNSB is offline