Date: Thu, 03 Jun 2021 16:11:51 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 256387] lang/tauthon: Update to 2.8.3 Message-ID: <bug-256387-7788-iV4MQkkd4S@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256387-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-256387-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256387 --- Comment #3 from Olivier Certner <olivier.freebsd@free.fr> --- Hi Fernando, On my side, yes, I never considered Tauthon dead, and I've even contributed= to it upstream. On portmgr's side, I don't know at all. Last information I have is portmgr public mail announcing deprecation ("Python 2.7 removal outline"). I'll just point out that python27 has an expiration date of 2020/12/31 but is still in the tree. Sure, no ports depend on Tauthon, since this was forbidden, so it= 's indeed technically trivial to remove it, whereas removing Python 2.7 would imply removing Chromium et alter. But I think this is irrelevant to the matter at hand. This new version of Tauthon fixes lots of security problems reported to Python 3.x, and as such should be imported before expiration, just for the fact that some people th= at want to use it will resurrect the port locally, so it's better they have the most recent version. And yes, this also means that Tauthon is now more secure than Python 2.7, a= nd even has fixes not yet in 3.x. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256387-7788-iV4MQkkd4S>