[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

Changes by Éric Araujo : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

R. David Murray added the comment: Yes, simply saying "make it consistent" is a won't fix, because of backward compatibility issues. Specific proposals for specific functions in a way that deals with the backward compatibility issues should be opened as new issues. -- nosy: +r.david.

[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

Éric Araujo added the comment: I’m afraid backward compatibility binds us here. For new code however, it would be nice to use one name consistently. My preference goes to “file”, because I really like the print function, but I suspect this could turn into bikeshedding quickly :) I think th

[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

Mark Lawrence added the comment: @Philip can you provide a patch so we can take this forward? -- nosy: +BreamoreBoy stage: -> needs patch versions: +Python 3.2 ___ Python tracker __

[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

Changes by Éric Araujo : -- nosy: +Merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue6226] Inconsistent 'file' vs 'stream' kwarg in pprint, other stdlibs

New submission from Philip Jenvey : It'd be nice to eventually standardize on the kwarg name used for basic file-like args in the stdlib. print, warnings.showwarning and some others take a file= argument whereas pprint, getpass.getpass take stream= print and pprint in particular should match