From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: [PATCH] Fix ob-python.el initiate session error with py-shell
Date: Thu, 20 Feb 2020 18:46:28 +0100
Message-ID: <87d0a95eyz.fsf@bzg.fr>
References: <877e0kjbqq.fsf@gmail.com> <874kvnako5.fsf@gmail.com>
 <871rqrak5y.fsf@gmail.com>
 <CAL1eYu+2MhYJq3fOduU1miefTiXtV+v0vtsJ=BobastLNnzyNg@mail.gmail.com>
 <87wo8ik22r.fsf@gmail.com> <87d0a995hp.fsf@gmail.com>
 <20aad61e-48e0-ba01-9255-793eacfdbc7e@easy-emacs.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:43645)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <bzg@gnu.org>) id 1j4puJ-0003vP-Dd
 for emacs-orgmode@gnu.org; Thu, 20 Feb 2020 12:46:40 -0500
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
To: Andreas =?utf-8?Q?R=C3=B6hler?= <andreas.roehler@easy-emacs.de>
Cc: Jack Kamm <jackkamm@gmail.com>, emacs-orgmode@gnu.org, python-mode@python.org

Hi all,

in future releases of Org, we will move toward stricter rules on what
to accept as ob-* libraries and what modes these libraries should rely
upon.

This was briefly mentioned in this email:
https://lists.gnu.org/archive/html/emacs-orgmode/2020-02/msg00714.html

For example, we can have a rule that we don't include ob-* libraries
for languages that are not somehow known by Emacs.  It would mean that
e.g. ob-clojure.el would have to live outside Org's core.

Also, for included ob-*, the idea would be to use the mode that are
bundled with Emacs core.  For Python, it would mean that ob-python.el
should support python.el, not python-mode.el.

This is not to say that python.el is better than python-mode.el: I
have no opinion on this and I'm confident both meet different users.

But that's something to consider.

We can always have another ob-python-mode.el file for users who use
python-mode.el: even the names would make it clear that Org babel uses
one mode and not the other.

I suggest we have the discussion on such rules after Org 9.4, but in
the meantime, this is something you may consider when fixing hacking
on ob-python.el.

Best,

-- 
 Bastien