PEP 813 - The Pretty Print Protocol

[barry (Barry Warsaw)]

@bitdancer

I don’t object to anything this pep does other than its questionable use of the name __pprint__ I’d also really like the __pprint__ I described above, but its absence wouldn’t be a reason to reject the PEP. What I want to emphasize, though, is that the things that return structured data should be decoupled from the pretty print concepts. Pretty print should use that data, but that data is not pretty print data.

Thanks for the detailed thoughts RDM^[1]. We’ll bikeshed on the methodname, and I think the salient point for where I envision this PEP is this last paragraph. All the suggestions you make would be quite useful, but is a more more elaborate proposal than what’s going on here. Which of course doesn’t mean it’s bad, just that it’s unlikely something I’d want to champion^[2].

So let’s focus in on the corner-painting and make sure that nothing we’re doing here can prevent such future directions, should someone want to pursue them.

---

1. and for the subtle callback to the email module for motivation! ↩︎

2. though I won’t speak for my co-conspirator ↩︎