Date: Wed, 28 Mar 2018 12:26:24 +0200 From: Guido Falsi <madpilot@FreeBSD.org> To: Pete Wright <pete@nomadlogic.org>, "D.-C. M." <my-roaming-data@outlook.com>, "kde@FreeBSD.org" <kde@FreeBSD.org> Cc: "ports@FreeBSD.org" <ports@FreeBSD.org> Subject: Re: FreeBSD Port: py27-qt5-core / Py36-qt5-core Message-ID: <9260edcd-c7af-593a-d342-21e1f578e683@FreeBSD.org> In-Reply-To: <67cf2069-85d7-7531-6177-e4d258009df9@nomadlogic.org> References: <AM5PR0901MB1139637F840990FAB019C890A9AC0@AM5PR0901MB1139.eurprd09.prod.outlook.com> <c600a76b-b01c-6a65-c0c4-ecb2bd7ff105@FreeBSD.org> <8b5a9d2d-3373-f164-9a1d-e3acf19e1ec9@nomadlogic.org> <71bf65f9-20ad-a30c-0fdd-bc78b31e666c@FreeBSD.org> <67cf2069-85d7-7531-6177-e4d258009df9@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/28/18 00:16, Pete Wright wrote: >>> Regardless, the clock is ticking on the 2.x codebase >>> as it is reaching EOL status in 2020: >>> >>> https://www.python.org/dev/peps/pep-0373/ >>> >>> Hopefully a solid deadline (which has already been pushed back) will >>> motivate developers to accelerate the task of migrating to py3 sooner >>> rather than later. >> Speaking strictly as the maintainer of the calibre port and having >> discovered just now about this deadline: >> >> I don't know what the calibre developer plans to do about this, I'm >> certainly unable to port calibre to python 3, so I will do the best to >> keep it working for as long as python 2.7 is available in the ports, or >> update the port to use python 3 once the upstream does port it to that >> version. >> > this is a really tricky situation to be in no doubt, i wonder if > surfacing concerns about the impending 2.x EOL with upstream maintainers > would be a good way to nudge them into supporting py3? it's certainly > possible that the deadline in pep-373 hasn't been widely disseminated to > the developer community? Looks like there is active work in the py-mechanize package to port it to python 3, most done by the calibre author himself, so it looks like he's performing steps required to move calibre to python 3...First he needs to fix dependencies. So maybe something is moving, even if slowly. > > i'm not super active in the python community to be honest - but in my > role as a systems engineer this is something i've highlighted with teams > whose code i help support and have had mixed success with. usually > along the lines of "hey, so py2.7 is EOL'ing in 2020 do we have a > document with our migration strategy?" Looks like the calibre developer is well informed, Let's see what time will bring us. 2020 isn't too far, but still some time has to go. -- Guido Falsi <madpilot@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9260edcd-c7af-593a-d342-21e1f578e683>