Thanks scott. I will look into it. I found john's solution easy though. On Tue, Aug 16, 2016 at 7:33 PM, Scott Bonds <sc...@ggr.com> wrote:
> I use pyenv to install multiple versions of python under a user account on > my OpenBSD boxes. > > https://github.com/yyuu/pyenv > > > On 08/16, Jay Patel wrote: > >> Oh.. okay.. That was my concern. Thanks. >> >> On Tue, Aug 16, 2016 at 2:11 PM, Stuart Henderson <s...@spacehopper.org> >> wrote: >> >> On 2016-08-16, Jay Patel <rockworl...@gmail.com> wrote: >>> > On Tue, Aug 16, 2016 at 12:28 PM, Stuart Henderson < >>> s...@spacehopper.org> >>> > wrote: >>> > >>> >> On 2016-08-16, Jay Patel <rockworl...@gmail.com> wrote: >>> >> > is there a way to get two python versions running on OpenBSD system? >>> and is >>> >> > it advisable to use it for production system or just follow packaged >>> python >>> >> > version for production? >>> >> >>> >> You can just "pkg_add python" and choose - things are setup so that >>> >> different branches (2.7, 3.4, 3.5) can coexist. >>> > >>> > I have requirement for my deployment to work with python 2.7.10 while >>> > pkg_add gives me 2.7.11. and for supervisor-3.2.0 from pkg_add requires >>> > python2.7.11 which contradicts for my deployment. >>> >>> Ah, I don't think we ran into anybody wanting to do that yet. >>> You could do a local build and install it under a different prefix >>> (avoiding /usr/local), but this gets a lot more complicated, and >>> not really something I'd want to do on a production system.
