Date: Tue, 2 Jun 2020 23:31:36 +0200 From: xpetrl <xpetrl@beepc.ch> To: freebsd-questions@freebsd.org Subject: Re: Migrating To Python 3.x Message-ID: <26e534c3-54cd-8f3e-6aa4-aec12d354c5c@beepc.ch> In-Reply-To: <CAM8r67Arp_RT7S-S%2Bxf1V%2BKS_iqapT=aTW3BHv3DUo3JLudkjA@mail.gmail.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> <CAM8r67Arp_RT7S-S%2Bxf1V%2BKS_iqapT=aTW3BHv3DUo3JLudkjA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I usually use Python VirtualEnv not to modify system packages and to keep > one or another separated from each other:-) The same here, ATM it still just work(tm) Python2 virtualenv is maybe safe for the next months / years, but how long? When packages are installed with pip2, a big warning is prompted telling Python2 is EOL.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26e534c3-54cd-8f3e-6aa4-aec12d354c5c>