Hi, Bastien <b...@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.
