Jack Kamm <jackk...@gmail.com> writes: > Liu Hui <liuhui1...@gmail.com> writes: > >> I think these objects need to be shown in a single column rather than >> two. Besides, if the python code becomes too complex finally, I think >> maintaining the python code outside the ob-python.el, as suggested by >> Ihor, is a good idea. > > Thanks for reporting these misbehaving examples. I think the root of the > problem is `org-babel-script-escape', which is too aggressive in > recursively converting strings to lists. We may need to rewrite our own > implementation for ob-python. > > Also, I agree that moving the python code to an external file will be > helpful in handling these more complex cases. > > I may leave these tasks for future patches. In the meantime, we may have > to recommend ":results verbatim" for these more complex cases that > ":results table" doesn't fully handle yet.
Pushed the patch now, with one final change: I decided to leave dict as string by default, converting to table only when ":results table" is explicitly set. I think it's better this way for now, because of the misbehaving examples you pointed out -- table conversion is not yet fully robust for complex dict's containing complicated objects or structures.
