Implement C's Switch in Python 3
PythonList at DancesWithMice.info
Sun Feb 3 04:08:52 EST 2019
On 3/02/19 9:45 PM, Chris Angelico wrote:
> On Sun, Feb 3, 2019 at 7:40 PM DL Neil <PythonList at danceswithmice.info> wrote:
>> This would normally see us coding "2019-02-03". The arrangement of
>> larger to ever more precise time-units is very useful in databases and
>> applications such as file-names, because it sequences logically.
>> However, that is not the way 'normal people' like to write their dates.
>> The trouble with 'common practice' though, is that it is localised.
>> There is great confusion between the way different cultures (even
>> staying within the English-speaking world) express dates. Is 3/2/2019
>> referring to "3rd February" or "March 2nd"?
> Which is why I always write dates in sorted format, usually eschewing
> //CJA 20160511: Is this still happening? I don't remember seeing it in
> three parts of forever.
Sure is. It is an acceptable alternative under the ISO standard.
Some would say it is more sensible to use when storing data because it
removes the dash/hyphen separators in exchange for implying the
fixed-format. (more bytes/characters saved if extend to include the time)
I'm not going there - recalling folk from these memory-is-cheap times
being less able to understand why we used to save 'expensive' storage
space by using yy-years (instead of ccyy) and thus 'causing' "the
millennium bug" aka Y2K!
I wouldn't use it in a 'visible' situation though, eg a fileNM. Yes, it
is shorter, but as my eyes age (they are already older than my teeth!),
I find it much slower to decode than reading the same with embedded
> That said, I am aware that I am not in any way a "normal person".
> Using month names as per your other example is probably a fair
> compromise with other humans.
There's normal and there's normal - like it's tomato or tomato?
More information about the Python-list