Date: Mon, 1 Jun 2020 22:52:25 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Migrating To Python 3.x Message-ID: <04c4ee18-daa2-aebc-882c-29407a58a160@tundraware.com> In-Reply-To: <0b794721-3548-0882-58ff-7eedd54fe645@tundraware.com> References: <02676140-06dd-a947-b7b4-0f6ccbeaf773@tundraware.com> <cdbae924-82d3-6d37-db4e-c9ed2ef9b1ab@kicp.uchicago.edu> <bfbe75c7-d53b-7a42-a4b9-36ad1585a39f@tundraware.com> <0b794721-3548-0882-58ff-7eedd54fe645@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/1/20 5:25 PM, Tim Daneliuk wrote: > On 6/1/20 5:17 PM, Tim Daneliuk wrote: >> What else did you manage in your mail server setup depend on the sneaky snake (python)? > > > Bind claims it needs it, but I suspect bind will be ok if I change the > default python version and reinstall. > > Samba says the same thing. > > A lot of the dependencies seems to be for mailman. > > So I was able to move everything over to python 3.7 _except_ mailman which, of course requires python 2.7. However, I keep running into the old problem that the setuptools for each of these versions conflict with each other because they install in the same location (why? everything else in multi-verion python lives under its own directory tree.) Until/unless I can figure out a reasonable way to work around this, everything either has to live under 2.7 past EOL or I cannot run mailman2 (which is not an option unless mailman3 gets ported). Has anyone every managed to get py2 and py3 to coexist happily on FreeBSD including their respective pips and setuptools? -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04c4ee18-daa2-aebc-882c-29407a58a160>