Date: Mon, 29 Jul 2013 14:30:24 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: David Demelier <demelier.david@gmail.com> Cc: ports@freebsd.org Subject: Re: python 2 and 3 modules Message-ID: <E1V3lei-000Bp9-H1@kabab.cs.huji.ac.il> In-Reply-To: <CAO%2BPfDcARya67Kd%2BhOEfDGNzLA4zp%2B8d1JYJhsYShQx=kXVijA@mail.gmail.com> References: <E1V3QJs-000JpR-FR@kabab.cs.huji.ac.il> <CAO%2BPfDcARya67Kd%2BhOEfDGNzLA4zp%2B8d1JYJhsYShQx=kXVijA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 2013/7/28 Daniel Braniss <danny@cs.huji.ac.il>: > > Hi, > > I need to be able to have both (2.7 and 3.2) modules. > > setting PYTHON_VERSION=3.2 in /etc/make.conf compiles properly, > > but make install, insists that that the 2.7 version is installed! > > after deinstalling, it will install the 3.2 version in the correct directory: > > /usr/local/lib/python3.2/site-path > > but now I lost the 2.7 version. > > > > the same happens if I try to install the 2.7 version, it will complain > > that the 3,2 version is installed. > > > > BTW, the comments in ports/Mk/bsd.python.mk are very confusing and > > some are wrong: > > # PYTHON_VERSION - Version of the python binary in your ${PATH}, in the > > # format "python2.0". Set this in your > > makefile in case you > > # want to build extensions with an > > older binary. > > # default: depends on the version of > > your python binary > > > > setting it to "python3.2" produces errors in the make, while 3.2 is ok > > > > is there any fix? > > > > thanks, > > danny > > > > For the moment its pretty difficult to install python 2.7 and 3.3 at > the same time. However, if you plan to install python 3.3, you need to > set PYTHON_DEFAULT_VERSION to "python3.3" and not PYTHON_VERSION. the joke on sysadmin/programes (im one of them) is that we give a correct answer to the wrong qwestion :-) the problem is not compiling modules(*), that works fine, it's the install. there is a bug somewhere, where the check if installed is WRONG, so it deinstalls the LAST installed module, but installes the correct version! my workaround was to tar lib/python2.7/site-packages, install the 3.2 modules (which deinstalls the 2.7) and when done, untar the 2.7. the virtualenv is a nogo here, we have several hundred users! the bsd.python.mk needs urgent cleanup, it's most confusing cheers, danny *: make PYTHON_VERSION=3.2 clean {de,re}install PS: keep me in the CC, I'm not subscrided to ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1V3lei-000Bp9-H1>