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: Sat, 13 Nov 2021 20:31:05 +0700 [thread overview]
Message-ID: <smoen0$u9b$1@ciao.gmane.io> (raw)
In-Reply-To: <875yswn5zj.fsf@gmail.com>
On 13/11/2021 09:22, Tim Cross wrote:
> Uwe Brauer writes:
>
> Given that Ubuntu 16.04 was end of life in April 2021, my recommendation
> would be to upgrade to ubuntu 21.04.
I would not recommend a release with end of support in January 2022 to a
person who is trying to avoid upgrading despite 18.04 and 20.04 long
time support releases are available.
From mails to this list my impression is that 5-years old OS generates
enough compatibility problems to seriously consider newer LTS version.
Support of python-2.7 and early 3.x version has been seized as well.
>> File "/usr/lib/python3/dist-packages/dateutil/parser.py", line 25, in <module>
>> from six import text_type, binary_type, integer_types
>> ModuleNotFoundError: No module named 'six'
^^^^^^^^^^^^^^^^^^^^^
Another question: does ipython babel backend in Org uses the same python
interpreter as python or it should be configured separately? Since you
are using ipython, do you have it installed for python versions you are
trying?
next prev parent reply other threads:[~2021-11-13 13:32 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 [this message]
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
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='smoen0$u9b$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).