emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: after installing python3.6 on Ubuntu 16.04, org files open with errors
Date: Sun, 14 Nov 2021 18:43:51 +0100	[thread overview]
Message-ID: <87o86mr5t4.fsf@mat.ucm.es> (raw)
In-Reply-To: smrg1c$13ro$1@ciao.gmane.io

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

>>> "MN" == Max Nikulin <manikulin@gmail.com> writes:

> 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.

I need still 2.7 to compile mercurial, since I rely on some extensions
for mercurial that do not work under 3.X 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2021-11-14 17:44 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
2021-11-14 17:43         ` Uwe Brauer [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87o86mr5t4.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).