You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prettyprint() function recursively moves over a jxmlease data structure and produces a new intermediate structure of native dicts and lists which is then feed into the standard pprint function (potentially using a small backup version instead). I wonder, would it not be better to split this in two parts, the first that generates the data structure and the second doing the prettyprinting. The reason I'm asking for this is that I think that intermediate data structure could come in handy, especially if it can be made to return OrderedDict, in converting to other data formats. Thoughts?
The text was updated successfully, but these errors were encountered:
plajjan
changed the title
Expose prettyprint data structure directly
Expose intermediate prettyprint data structure directly
Mar 16, 2017
The prettyprint() function recursively moves over a jxmlease data structure and produces a new intermediate structure of native dicts and lists which is then feed into the standard pprint function (potentially using a small backup version instead). I wonder, would it not be better to split this in two parts, the first that generates the data structure and the second doing the prettyprinting. The reason I'm asking for this is that I think that intermediate data structure could come in handy, especially if it can be made to return OrderedDict, in converting to other data formats. Thoughts?
The text was updated successfully, but these errors were encountered: