Date: Thu, 30 Apr 2020 02:03:20 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: mail/mailman v3? Message-ID: <6d669657-05fb-df71-000a-f67523609327@gmx.de> In-Reply-To: <eec989d7f0083b21b5f2d9f2438261fc@udns.ultimatedns.net> References: <eec989d7f0083b21b5f2d9f2438261fc@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.04.20 um 22:02 schrieb Chris: > In sentiment I am inline with your thoughts as well. > Would it be a worthy project to create a mailman(2)-lts port? > I'd be fully up for helping, and or creating it myself. > There's a port that's a shim for py2.x-->py3.x called 2to3, or somethin= g > like that. It also wouldn't be that difficult to simply modify mailman(= 2) > to adopt the py3.x language changes.=20 Given that Mailman is mainly a text processing machine with various heads (mail, web and CGI, command line) interfaces, and one of the ideas driving the incompatible Python 3 was to clean up the delineation of the strings/bytes/unicode types from one another and see to encoding. we'd be in for lots of - ironically speaking - "fun" - meaning code audits, revisions, possibly explicit code to write for the front lines to properly decode external input and encode internal output. I haven't looked into too much detail, but attaining 100% conversion and test coverage would be a challenge and possibly a major undertaking. I'd assume had it been as simple as 2to3 or py-futurize or adopting py-six, someone might have done that already.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6d669657-05fb-df71-000a-f67523609327>