pep 8 constants

Steven D'Aprano steve at
Mon Jun 29 20:11:02 EDT 2009

On Mon, 29 Jun 2009 11:49:04 -0400, Eric S. Johansson wrote:

> alex23 wrote:
>> "Eric S. Johansson" <e... at> wrote:
>>> no, I know the value if convention when editors can't tell you
>>> anything about the name in question.  I would like to see more support
>>> for disabled programmers like myself and the thousands of programmers
>>> injured every year and forced to leave the field.  seriously, there is
>>> no money in disability access especially for programmers.
>> Well, if we can't use conventions like uppercasing, camelcasing and
>> underscoring, what are you recommending we do instead?
> help build a smart editing environment please.

Why do you think a smart editing environment is in opposition to coding 
conventions? Surely an editor smart enough to know a variable name spoken 
as "pear tree" is an instance and therefore spelled as pear_tree (to use 
your own example) would be smart enough to know a variable name spoken as 
"red" is a constant and therefore spelled "RED"?

Sounds to me that your speech environment needs a command to turn 
capslock on and off, and your problem with PEP 8 is solved:

x equals caps on red caps off plus three

> Heck, have you ever noticed how most Python smart editors can't even
> indent properly according to local contexts. Emacs is the only one and
> even that one sometimes fails

I use kwrite for editing, and I can't say I've ever noticed a failure.

> I've lived this works and probably have put more deep thought and 8kloc
> into it because I do not accept circures tricks as a way of life.  I
> want it to work right and I know how to do it.  I just don't have the
> hands and hte money to pay me to do it.

You're using a speech interface, right? You've written about "putting a 
gun to your wrists", said you can't follow PEP 8 because it's not voice 
safe, and generally given the impression that you can't use a keyboard.

So... just how do you get "hte" from saying "the"?

If you are using a keyboard to type this post, then surely it's not such 
a huge imposition to type a couple of words in all caps here and there 
while you speak the rest of the code?

<speak> x equals </speak> <type> <caplock> R E D </type> <speak> plus 
three </speak>

I know that doesn't resolve the issue for those people who truly can't 
use a keyboard at all, even for a single character, but it's unfair to 
insist that the only permitted coding conventions are the ones suitable 
for the tiny minority who, frankly, are going to have problems no matter 
what coding conventions we have.

Especially when these coding conventions are entirely optional.


More information about the Python-list mailing list