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


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

Re: Python Worst Practices

Started byJoel Goldstick <joel.goldstick@gmail.com>
First post2015-02-25 17:59 -0500
Last post2015-02-25 17:59 -0500
Articles 1 — 1 participant

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 Joel Goldstick <joel.goldstick@gmail.com> - 2015-02-25 17:59 -0500

#86444 — Re: Python Worst Practices

FromJoel Goldstick <joel.goldstick@gmail.com>
Date2015-02-25 17:59 -0500
SubjectRe: Python Worst Practices
Message-ID<mailman.19220.1424905154.18130.python-list@python.org>
On Wed, Feb 25, 2015 at 4:28 PM, 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, 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
>
> 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.
>
> --
> https://mail.python.org/mailman/listinfo/python-list



-- 
Joel Goldstick
http://joelgoldstick.com

[toc] | [standalone]


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


csiph-web