From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jack Kamm <jackkamm@gmail.com>
Subject: Re: [PATCH] Fix ob-python.el initiate session error with py-shell
Date: Thu, 20 Feb 2020 10:51:23 -0800
Message-ID: <87k14hjdn8.fsf@gmail.com>
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> <87d0a95eyz.fsf@bzg.fr>
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]:52956)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <jackkamm@gmail.com>) id 1j4qv4-0001eu-Ig
 for emacs-orgmode@gnu.org; Thu, 20 Feb 2020 13:51:32 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <jackkamm@gmail.com>) id 1j4qv3-0006fP-If
 for emacs-orgmode@gnu.org; Thu, 20 Feb 2020 13:51:30 -0500
In-Reply-To: <87d0a95eyz.fsf@bzg.fr>
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: Bastien <bzg@gnu.org>, Andreas =?utf-8?Q?R=C3=B6hler?= <andreas.roehler@easy-emacs.de>
Cc: emacs-orgmode@gnu.org, python-mode@python.org

Hi,

Bastien <bzg@gnu.org> writes:

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

I agree that ob-python.el should only rely on functionality from
python.el, and shouldn't need to know about other packages. This will
reduce the maintenance burden for ourselves.

At the same time, I would like the user to use whatever Python-related
modes they like when editing the org Python source buffer, such as
python-mode.el, elpy, etc., without issue. That doesn't mean that we'll
put workarounds and references to external packages in ob-python.el, but
rather that we'd keep ob-python simple and easy for external packages to
interop with.

I think this is more or less the case today, and we're on the same page
here. Just wanted to make this goal explicit.