From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [SOLVED] (was: [downgrading to matlab 2019a and using 3.5 NOW does not work neither])
Date: Mon, 15 Nov 2021 21:51:32 +0700 [thread overview]
Message-ID: <smts5m$tat$1@ciao.gmane.io> (raw)
In-Reply-To: <875ystsfyv.fsf_-_@mat.ucm.es>
On 15/11/2021 20:31, Uwe Brauer wrote:
> Advice: don't try to upgrade python on a given Ubuntu distribution!!!!
Anover advice:
1. Avoid unsupported versions of software (Ubuntu-16.04 has only payed
support for more than a year) and localize its usage if there is no
other way.
> * reinstall jupyter
>
> #+begin_src
> sudo dpkg --purge python3-ptyprocess
> sudo -H pip3 install --upgrade --force-reinstall --no-cache-dir jupyter
2. Use venv (virtualenv for Python-2.7) to keep packages installed by
pip isolated from system .deb's.
> I need still 2.7 to compile mercurial, since I rely on some extensions
> for mercurial that do not work under 3.X
Ubuntu-20.04 has (already unsupported) Python-2.7 in addition to 3.8 and
3.9.
It is better to keep primary system up to date and to use containers
(LXC, docker, etc.) or fully virtualized systems for special needs.
prev parent reply other threads:[~2021-11-15 14:52 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
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 [this message]
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='smts5m$tat$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).