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


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

Re: Python Worst Practices

Started byChris Angelico <rosuav@gmail.com>
First post2015-02-26 14:17 +1100
Last post2015-02-26 14:17 +1100
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 Chris Angelico <rosuav@gmail.com> - 2015-02-26 14:17 +1100

#86466 — Re: Python Worst Practices

FromChris Angelico <rosuav@gmail.com>
Date2015-02-26 14:17 +1100
SubjectRe: Python Worst Practices
Message-ID<mailman.19235.1424920639.18130.python-list@python.org>
On Thu, Feb 26, 2015 at 2:05 PM, Dave Angel <davea@davea.name> wrote:
> On 02/25/2015 08:44 PM, Mark Lawrence wrote:
>>
>> On 25/02/2015 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?
>>>
>>
>> Throwing in my own, how about built-in functions should not use "object"
>> as the one and only argument, and a keyword argument at that.
>>
>
> def marry(object = False)...
>
>
> if anybody has any cause to object, let him speak now...

Python.

Python is what bwings us togethar, today.

And def, twue def, will make your argument into a keyword argument
that will fowwow you forevah and evah. So tweasure your keyword
arguments...

ChrisA

[toc] | [standalone]


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


csiph-web