Date: Tue, 2 Jun 2020 11:05:36 +0200 From: Tomasz CEDRO <tomek@cedro.info> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Migrating To Python 3.x Message-ID: <CAM8r67Arp_RT7S-S%2Bxf1V%2BKS_iqapT=aTW3BHv3DUo3JLudkjA@mail.gmail.com> In-Reply-To: <04c4ee18-daa2-aebc-882c-29407a58a160@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> <04c4ee18-daa2-aebc-882c-29407a58a160@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
wt., 2 cze 2020, 05:54 u=C5=BCytkownik Tim Daneliuk Has anyone every managed to get py2 and py3 to coexist happily on FreeBSD including their respective pips and setuptools? I usually use Python VirtualEnv not to modify system packages and to keep one or another separated from each other :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM8r67Arp_RT7S-S%2Bxf1V%2BKS_iqapT=aTW3BHv3DUo3JLudkjA>