Date: Thu, 4 Jun 2020 00:55:34 -0500 From: Doug McIntyre <merlyn@geeks.org> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Migrating To Python 3.x Message-ID: <20200604055534.GA40717@geeks.org> In-Reply-To: <20200602040748.ewkrdmnk6qrq2vn6@ozzmosis.com> References: <02676140-06dd-a947-b7b4-0f6ccbeaf773@tundraware.com> <20200602040748.ewkrdmnk6qrq2vn6@ozzmosis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 02, 2020 at 02:07:48PM +1000, andrew clarke wrote: > On 2020-06-01 17:03:50, Tim Daneliuk (tundra@tundraware.com) wrote: > > > I have a number of servers with rather complex mail/dns/web server > > configurations that are stable and have been running happily for many years > > needing nothing more than monthly patching. > > > > But Python 2.x is EOL at the end of this year. Can anyone suggest a > > strategy for moving from 2.x to 3.x? > > > > Also concerned about what to do with mailman since mailman3 never has made > > it to the ports tree as best as I can determine. > > I notice there's a PR for adding mail/mailman3 to Ports: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225543 > > Though work dates back to 2018 and seems to have stalled. Presumably it needs > feedback/testing/feeding. :-) mailman3 is not mailman2++. mailman3 needs fixing to be more than a developer work-in-progress. Best to look at some of the alternatives mentioned earlier in the thread, or become a developer to make it a workable product.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200604055534.GA40717>