any plans to make pprint() a builtin?
johnjsal at NOSPAMgmail.com
Mon May 15 16:48:03 CEST 2006
> Considering that the current:
> import pprint
> is hardly lengthy, I can't see how either of the alternatives proposed
> are any better.
> 6 characters shorter, but considerably more keystrokes if you are using
> pprint more than once. Is it worth adding the 'python' builtin to save
> an import statement?
>> import py
> Longer, messy, and what's the actual point? Wouldn't:
> import pprint as pp
> be better, standard *and* shorter?
I guess the idea is that you can use the import py statement to access
many other modules as well, without importing them all separately.
More information about the Python-list