Re: Python (Multi) installation?

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I don't quite follow this. I have a system, where initially I did not
have PYTHON_VERSION_DEFAULT defined; various packages brought
python2.7 and a bunch of py27-xxxx packages. Subsequently I needed
python3 for something, I installed python36 and set the above
environment variable to 36. I then also had to install many additional
python packages, which came as py36-xxx, of course. There were a few
other packages explicitly requiring python2, which were built despite
3.6 being the default one. Later, when python3.7 came out, installed
it as well - the three versions seem to coexist for me. the default is
still 36, but if I need a specific python package for 37, I set the
above variable in the environment to 37 and carry on with the build. I
have at the same time, e.g., idle2.7, idle3.6 and idle3.7.

I was thinking of replacing everything 3.6 with 3.7, but wasn't sure
if all the packages build for the latter so left it for later.

I also recently replaced all p5-xxx modules from 5.6.2 to 5.8... That
was a bit of a trouble, as the packages themselves were not enough, I
had to search all other packages bringing perl modules into the site
library. I don't think pkg_rolling-replace can easily do this.
On Sat, 15 Sep 2018 at 22:03, John D. Baker <jdbaker%mylinuxisp.com@localhost> wrote:
>
> Besides "Confuse-a-pkg_chk (LTD)", I recall another interesting bit with
> multiple python versions.
>
> Various glib/gtk things seem now to want python37 either directly or
> indirectly.  ISTR that python37 wouldn't install because there was
> already a python36 installed, courtesy of LibreOffice.
>
> So I figured the path of least resistance was to 'pkg_delete -R libreoffice'.
> Then python37 and the various py37-* packages installed fine.
>
> Then I went back to re-install LibreOffice.  It requires python3x where
> 0<=x<=6 -- python37 is right out.  I was anticipating a complaint that
> python36 could not be installed since python37 was already installed,
> but such did not happen.
>
> Could it be the failure to install python37 with an existing python36
> was because the python36 install predated the availability of python37
> and so raised a conflict?
>
> Perhaps explicitly rebuild/replace python36 early will remove conflict
> when python37 is to be installed?
>
> --
> |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
> |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
> | X  No HTML/proprietary data in email.   BSD just sits there and works!
> |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645
>


-- 
----