[Python-ideas] AMEND PEP-8 TO DISCOURAGE ALL CAPS
bruce at leban.us
Wed Jan 30 15:01:17 EST 2019
Text in color or against black backgrounds is harder to read than black on
See for example:
Text where different words in the same sentence are in different colors is
even harder to read.
And I think we should totally ban anyone on the web from putting light gray
text on a lighter gray background
(see https://www.wired.com/2016/10/how-the-web-became-unreadable/ for a
Or to say that another way:
I think we should totally ban anyone on the web from putting light gray
text on a lighter gray background!!
But many of us use editors that use color for syntax highlighting and we do
that because projecting semantics onto the color axis works for us. So we
don't ban colorizing text and we shouldn't.
Capitalizing constants may be slightly harder to read but constants in code
are the minority and emphasizing them is precisely the point.
I'm MINUS_ONE on changing PEP 8. Make your own styleguide if you don't want
to follow PEP 8 in your code.
On Wed, Jan 30, 2019 at 11:48 AM Abe Dillon <abedillon at gmail.com> wrote:
> > Is it that really obnoxious?
> > Does using upper case for constants measurably slows down coders? Can
> you cite the actual papers describing such experiments that lead to this
> conclusion ?
> > from my experience having a visual clue that a value is a constant or an
> enum is something pretty useful.
> Do you have any proof that it's useful? Have you ever been tempted to
> modify math.pi or math.e simply because they're lower case? Have you ever
> stopped to wonder if those values change?
> If the socket library used packet_host, packet_broadcast, etc. instead of
> PACKET_HOST, PACKET_BROADCAST, ETC. would you be confused about whether
> it's a good idea to rebind those variables? Would you be tempted to write
> the line of code: socket.packet_host = x?
> It seems to me that nobody is actually considering what I'm actually
> talking about very carefully. They just assume that because all caps is
> used to convey information that information is actually important. Not just
> important, but important enough that it should be in PEP-8. They say I
> should just violate PEP-8 because it's not strictly enforced. It is
> strictly enforced in workplaces. I don't see why it can't be the other way
> around: PEP-8 doesn't say to use all caps, but if you want to it's OK.
> > Surely, I'd hate reading a newspaper article where the editor generously
> sprinkled upper case words everywhere
> Exactly. If it's an eye-sore in every other medium, then it seems likely
> to me, the only reason programmers don't consider it an eye-sore is they've
> become inured to it.
> > but analogies only go so far, reading code have some similarities with
> reading prose, but still is not the same activity.
> CAN you articulate what is DIFFERENT about READING code that makes the ALL
> CAPS STYLE less offensive?
> On Tue, Jan 29, 2019 at 6:09 PM Marcos Eliziario <
> marcos.eliziario at gmail.com> wrote:
>> Is it that really obnoxious? Does using upper case for constants
>> measurably slows down coders? Can you cite the actual papers describing
>> such experiments that lead to this conclusion ?
>> Because, from my experience having a visual clue that a value is a
>> constant or an enum is something pretty useful.
>> Surely, I'd hate reading a newspaper article where the editor generously
>> sprinkled upper case words everywhere, but analogies only go so far,
>> reading code have some similarities with reading prose, but still is not
>> the same activity.
>> Marcos Eliziario
>> Em ter, 29 de jan de 2019 às 20:30, Cameron Simpson <cs at cskk.id.au>
>>> On 29Jan2019 15:44, Jamesie Pic <jpic at yourlabs.org> wrote:
>>> >On Fri, Jan 4, 2019 at 10:07 PM Bernardo Sulzbach
>>> ><bernardo at bernardosulzbach.com> wrote:
>>> >> I'd suggest violating PEP-8 instead of trying to change it.
>>> >TBH even my bash global environment variables tend to become more and
>>> >more lowercase ...
>>> If you mean _exported_ variables, then this is actually a really bad
>>> The shell (sh, bash, ksh etc) makes no enforcement about naming for
>>> exported vs unexported variables. And the exported namespace ($PATH etc)
>>> is totally open ended, because any programme might expect arbitrary
>>> optional exported names for easy tuning of defaults.
>>> So, you think, since I only use variables I intend and only export
>>> variables I plan to, I can do what I like. Example script:
>>> export b
>>> So $b is now exported to subcommands, but not $a.
>>> However: the "exported set" is initially the environment you inherit.
>>> Which means:
>>> Any variable that _arrives_ in the environment is _already_ in the
>>> exported set. So, another script:
>>> # not exporting either
>>> If that gets called from the environment where you'd exported $b (eg
>>> from the first script, which could easily be your ~/.profile or
>>> ~/.bashrc), then $b gets _modified_ and _exported_ to subcommands, even
>>> though you hadn't asked. Because it came in initially from the
>>> This means that you don't directly control what is local to the script
>>> and what is exported (and thus can affect other scripts).
>>> The _only_ way to maintain sanity is the existing convention: local
>>> script variables use lowercase names and exported variables use
>>> UPPERCASE names. With that in hand, and cooperation from everyone else,
>>> you have predictable and reliable behaviour. And you have a nice visual
>>> distinction in your code because you know immediately (by convention)
>>> whether a variable is exported or not.
>>> By exporting lowercase variables you violate this convention, and make
>>> your script environment unsafe for others to use.
>>> Do many many example scripts on the web do the reverse: using UPPERCASE
>>> names for local script variables? Yes they do, and they do a disservice
>>> to everyone.
>>> Cameron Simpson <cs at cskk.id.au>
>>> Python-ideas mailing list
>>> Python-ideas at python.org
>>> Code of Conduct: http://python.org/psf/codeofconduct/
>> Marcos Eliziário Santos
>> mobile/whatsapp/telegram: +55(21) 9-8027-0156
>> skype: marcos.eliziario at gmail.com
>> linked-in : https://www.linkedin.com/in/eliziario/
>> Python-ideas mailing list
>> Python-ideas at python.org
>> Code of Conduct: http://python.org/psf/codeofconduct/
> Python-ideas mailing list
> Python-ideas at python.org
> Code of Conduct: http://python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas