Python Worst Practices

[alister]

On Wed, 25 Feb 2015 23:34:29 +0000, MRAB wrote:

> On 2015-02-25 22:59, Joel Goldstick wrote:
>  > On Wed, Feb 25, 2015 at 4:28 PM, MRAB <python at 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, so that might be a better example of
>  > > numbers that aren't really numbers.
>  >
>  > US zip codes get messed up with ints because many have a leading
>  > zero.
>  > I use strings
> 
> Telephone numbers can also start with zero.

unless you are performing maths on it data that is made up of numbers 
(zip code, tel number, house number etc) is still only text & should be 
stored as a string.

> 
 >  > > 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.
>  > >





-- 
To save a single life is better than to build a seven story pagoda.