Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><code>camelCase</code> and/or <code>CamelCase</code> (and that's a debate in its own right;-) may be overwhelmingly most popular for the kind of environments <em>you</em> are most familiar with, but that hardly makes them universal -- or have you never heard of the obscure language called C++, with its <code>std::find_first_of</code> and <code>std::replace_copy_if</code> algorithms and so on?!</p> <p>So there's no "deviation", as you state, in PEP 8 -- simply a choice towards the C++-standard conventions against the ones more popular in, say, Java or C#.</p> <p>As for what you should do for your own code, just pick a convention and stick with it -- consistency's more important than other considerations. My employer uses a <code>CamelCase</code> convention across all languages for all internal sources (though not necessarily when it comes to exposing public APIs, which is a separate issue), I personally detest it (I wish I could destroy <em>every</em> reliance on case sensitivity across the programming universe!-), but I stick to it, and actually help enforce it (in code reviews), because uniformity <strong>is</strong> important.</p> <p>I guess you'll understand why relying on case sensitivity is a horrible idea only if and when you have to rely on a screen reader to read code out to you -- most screen readers do a horrible job at pinpointing case issues, and there's no really good way, no strong or easy convention to convert case differences to easy auditory clues (while translating underscores to "clicks", in a good configurable screen reader, makes it a breeze). For people without any visual impairments whatsoever, which is no doubt 90% or more, you don't need to care (unless you want to be inclusive and help people who <strong>don't</strong> share your gift of perfect vision... naah, who cares about <strong>those</strong> guys, right?!).</p> <p>But, consistency is still important, and helps _every_body.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload