[Python-ideas] PEP 3155 - Qualified name for classes and functions
Barry Warsaw
barry at python.org
Tue Nov 8 16:55:40 CET 2011
In general, one problem with abbreviations is that they are more difficult for
non-native English speakers to understand and use. I've often heard such
complaints from acquaintances for whom English is not their primary language.
The other problem is that while *you* know what the 'q' stands for because you
derived it from the underlying concept, someone who stumbles over it in the
opposite direction will not know what it means. Maybe they'll search for it,
but otherwise, it'll just be a meaningless combination of characters.
Python has always valued readability over writing convenience, and I think
this is one of Guido's founding brilliant insights: code is read far more
often then it is written. And yet, he managed to find elegant ways of
expressing code clearly without being overly verbose.
For these reasons, I strongly believe that this attribute should not be
abbreviated.
If the spelled out name is too long, find another one that conveys the same
information in fewer characters. Several have been proposed and it's not hard
to find others. E.g. __name_details__.
(I personally do not have a problem with underscores separating the words.
Again, it makes it more clear, where as mashwords can be difficult to scan.)
Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20111108/ac1a4070/attachment.pgp>
More information about the Python-ideas
mailing list