This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients eric.araujo, pjenvey
Date 2010-11-12.01:11:09
SpamBayes Score 3.0575352e-06
Marked as misclassified No
Message-id <1289524270.84.0.865111721752.issue6226@psf.upfronthosting.co.za>
In-reply-to
Content
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 this is too little an issue to warrant a line in the style guide.  Maybe just watch python-checkins and comment when someone adds a function using “stream”, “fp” or “fileobj”.  I suggest closing this report as wontfix.

You may want to open a new report about the matter of pprint and print having incompatible signatures.  How about proposing a new function, say pprint.print, which could be a drop-in replacement for builtins.print?
History
Date User Action Args
2010-11-12 01:11:10eric.araujosetrecipients: + eric.araujo, pjenvey
2010-11-12 01:11:10eric.araujosetmessageid: <1289524270.84.0.865111721752.issue6226@psf.upfronthosting.co.za>
2010-11-12 01:11:10eric.araujolinkissue6226 messages
2010-11-12 01:11:09eric.araujocreate