gerard.vermeu...@posteo.net writes: > I do not know how much this "abuse" of defconst is frowned > upon (elisp manual says defconst is advisory), but maybe it > can be advertised as a feature.
org-babel-python--def-format-value is a "private" variable (it has double dash "--" in its name). Therefore it's not generally recommended to modify it. Of course, elisp doesn't have true private variables or functions, and you are free to change things as you wish -- this is one of the perks of Emacs :) But you've been warned, since this is a private variable, we make no guarantees, and may break things in backward-incompatible ways in the future. As to the broader point, I agree there are many more features that would be nice to add ob-python results handling. But making ob-python too complex will be difficult to maintain, especially since the Python code is all in quoted strings without proper linting. So I am thinking now about how we could make this more extensible in future. One idea is to create a Python package for interfacing with Org Babel, and release it on PyPi. If we detect the package is installed, then we can delegate to it for results formatting. And the community could contribute results handling for all sorts of Python objects to that package. That is just one idea for improving extensibility -- I'm not sure it's the best, and am open to other suggestions as well.
