[issue36705] Unexpected Behaviour of pprint.pprint

2019-04-23 Thread Fred L. Drake, Jr.
Fred L. Drake, Jr. added the comment: Eric nailed it; pprint was not designed as a replacement for print, and was never intended to serve that purpose. Rejecting as out of scope. -- resolution: -> rejected stage: -> resolved status: open -> closed _

[issue36705] Unexpected Behaviour of pprint.pprint

2019-04-23 Thread Eric V. Smith
Eric V. Smith added the comment: pprint.pprint is not designed to be a drop-in replacement for print. At this point, we cannot break existing code to change how pprint works. I suggest you make a pprint.pprint wrapper that does what you want, or maybe subclass pprint.PrettyPrinter.

[issue36705] Unexpected Behaviour of pprint.pprint

2019-04-23 Thread Gavin D'souza
Gavin D'souza added the comment: if pprint is called without parameters, it returns a TypeError >>> pprint() Traceback (most recent call last): File "", line 1, in TypeError: pprint() missing 1 required positional argument: 'object' it would be beneficial however to return an empty string

[issue36705] Unexpected Behaviour of pprint.pprint

2019-04-23 Thread Gavin D'souza
New submission from Gavin D'souza : For a simple string input, pprint would be expected to return an output similar to print. However, the functionality differs ### Code: import time from pprint import pprint start = time.time() time.sleep(0.5) object_made = time.time() time.sleep(0.5) done =