Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #86443 > unrolled thread

Re: Python Worst Practices

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Python Worst Practices MRAB <python@mrabarnett.plus.com> - 2015-02-25 21:28 +0000
    Re: Python Worst Practices Grant Edwards <invalid@invalid.invalid> - 2015-02-25 23:00 +0000
    Re: Python Worst Practices wxjmfauth@gmail.com - 2015-02-25 23:03 -0800

#86443 — Re: Python Worst Practices

On 2015-02-25 20:45, Mark Lawrence wrote:
> http://www.slideshare.net/pydanny/python-worst-practices
>
> Any that should be added to this list?  Any that be removed as not that bad?
>
We don't have numeric ZIP codes in the UK, but the entire world has
numeric telephone numbers, so that might be a better example of numbers
that aren't really numbers.

Numeric dates can be ambiguous: dd/mm/yyyy or mm/dd/yyyy? The ISO
standard is clearer: yyyy-mm-dd.

Handling text: "Unicode sandwich".

UTF-8 is better than legacy encodings.

[toc] | [next] | [standalone]

#86445

On 2015-02-25, MRAB <python@mrabarnett.plus.com> wrote:
> On 2015-02-25 20:45, Mark Lawrence wrote:
>> http://www.slideshare.net/pydanny/python-worst-practices
>>
>> Any that should be added to this list?  Any that be removed as not that bad?
>
> We don't have numeric ZIP codes in the UK, but the entire world has
> numeric telephone numbers,

That's probably true now, but hasn't always been the case (at least in
the US). If you're dealing with historical data, you might need to
include the city and exchange name in addition to the 4/5-digit line
number.  In _most_ multi-exchange service areas, those exchange names
have always mapped to a 2-digit number, but I believe there were
exceptions.

When I were a wee kid in the 60's my phone number was "Cedar 2 <yadda
yadda yadda yadda>". By then everybody had all-numeric dialing and
"Cedar" translated to "23", but it was still common to see phone
numbers printed using the exchange names.

> so that might be a better example of numbers that aren't really
> numbers.

-- 
Grant Edwards               grant.b.edwards        Yow! Am I elected yet?
                                  at               
                              gmail.com            

[toc] | [prev] | [next] | [standalone]

#86480

Le mercredi 25 février 2015 22:29:06 UTC+1, MRAB a écrit :
> On 2015-02-25 20:45, Mark Lawrence wrote:
> > http://www.slideshare.net/pydanny/python-worst-practices
> >
> > Any that should be added to this list?  Any that be removed as not that bad?
> >
> We don't have numeric ZIP codes in the UK, but the entire world has
> numeric telephone numbers, so that might be a better example of numbers
> that aren't really numbers.
> 
> Numeric dates can be ambiguous: dd/mm/yyyy or mm/dd/yyyy? The ISO
> standard is clearer: yyyy-mm-dd.
> 
> Handling text: "Unicode sandwich".
> 
> UTF-8 is better than legacy encodings.

I'm on the Unicode side.
Unfortunately and objectively, I can not share this
opinion. Most of people on this planet are not narrow
minded ascii user.

And what to say about the disastrous Unicode implementation
of Unicode in Python?

See https://groups.google.com/forum/#!topic/comp.lang.python/Avq1gRc2dzE

jmf

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web