emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: after installing python3.6 on Ubuntu 16.04, org files open with errors
Date: Mon, 15 Nov 2021 00:12:09 +0700	[thread overview]
Message-ID: <smrg1c$13ro$1@ciao.gmane.io> (raw)
In-Reply-To: <8735nz6gc3.fsf@gmail.com>

On 14/11/2021 01:39, Tim Cross wrote:
> Uwe Brauer writes:
>> Well in that case I'd rather would prefer 20.04 a LTS release. From
>> experience I know it will take me days till everything is working again,
>> but maybe it is time to do that step.
> I would check what the status was with Python in 20.04. I'm not sure
> they had completed the migration to v3 at that point and it was still a
> mixed v2/v3 setup. Pretty sure by 21.04 it was all v3.

Ubuntu-20.04: Python-3.8 is default, python-3.9 is available. Inkscape 
depends on python2:any.

dpkg -S /usr/bin/python
python-is-python2: /usr/bin/python

I have not noticed any problem with python3.

If some packages are considered as too old, e.g. Emacs-26.3 then 
Ubuntu-21.10 should be considered. At least it will be possible to 
upgrade it to Ubuntu-22.04 LTS in a single hop. Another option for rare 
upgrades is Debian stable.

> One thing I do find useful is to upgrade a virtual first. I use
> virt-manager to create a virtual machine running my current version and
> then upgrade that to see how the upgrade goes.

I tried Ubuntu-20.10 and Ubuntu-21.10 in qemu. With the former I faced a 
really weird bug with depressed shift in gdm3 password field (you have 
no chance to notice that only first letter typed with shift is 
capitalized), with the latter firefox does not always redraw tabs after 
switching them using Ctrl+PgUp or Ctrl+PgDown. Booting live image 
directly works better and allows to test hardware support, e.g. sound. I 
have not tried 21.10 in this way, with 20.10 default wayland session 
cursor on the external monitor was too huge to make point where it 
points to rather uncertain.

Problems with upgrade are usually caused by rarely used packages. So 
unless precise configuration is tried (dpkg --get-selections, dpkg 
--set-selections, third-party packages), the problem will not be noticed 
in VM. On the other hand installing all packages makes image size 
noticeably large.

>> That issue I could solve meanwhile but only to receive another error
>> ipython3 from my Ubuntu distribution but that corresponds to python 3.5
>> not 3.6 hm, ☹️ 

ipython may be installed to python 3.6 as well.

  reply	other threads:[~2021-11-14 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 22:15 after installing python3.6 on Ubuntu 16.04, org files open with errors Uwe Brauer
2021-11-13  2:22 ` Tim Cross
2021-11-13  9:59   ` Martin Schöön
2021-11-13 15:39     ` Uwe Brauer
2021-11-13 13:31   ` Max Nikulin
2021-11-13 15:48     ` Uwe Brauer
2021-11-13 15:38   ` Uwe Brauer
2021-11-13 18:39     ` Tim Cross
2021-11-14 17:12       ` Max Nikulin [this message]
2021-11-14 17:43         ` Uwe Brauer
2021-11-14 17:49 ` [downgrading to matlab 2019a and using 3.5 NOW does not work neither] (was: after installing python3.6 on Ubuntu 16.04, org files open with errors) Uwe Brauer
2021-11-15 13:31   ` [SOLVED] (was: [downgrading to matlab 2019a and using 3.5 NOW does not work neither]) Uwe Brauer
2021-11-15 14:51     ` Max Nikulin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='smrg1c$13ro$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).