Re: python function parameters, debugging, comments, etc.

From	Rotwang <sg552@hotmail.co.uk>
Newsgroups	comp.lang.python
Subject	Re: python function parameters, debugging, comments, etc.
Date	2013-10-02 14:52 +0100
Organization	A noiseless patient Spider
Message-ID	<l2h8f0$np2$1@dont-email.me> (permalink)
References	<mailman.576.1380668112.18130.python-list@python.org> <l2fmrk$4ti$1@dont-email.me> <mailman.605.1380708933.18130.python-list@python.org>

Show all headers | View raw

On 02/10/2013 11:15, Oscar Benjamin wrote:
> On 2 October 2013 00:45, Rotwang <sg552@hotmail.co.uk> wrote:
>>
>> So the upside of duck-typing is clear. But as you've already discovered, so
>> is the downside: Python's dynamic nature means that there's no way for the
>> interpreter to know what kind of arguments a function will accept, and so a
>> user of any function relies on the function having clear documentation.
>
> It is still necessary to document the arguments of functions in
> explicitly typed languages. Knowing that you need a list of strings
> does not mean that you know what the function expects of the values of
> the strings and what it will try to do with them.
>
> [...]

Well, yes. I didn't intend to suggest otherwise.

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

python function parameters, debugging, comments, etc. Chris Friesen <cbf123@mail.usask.ca> - 2013-10-01 16:54 -0600
  Re: python function parameters, debugging, comments, etc. Rotwang <sg552@hotmail.co.uk> - 2013-10-02 00:45 +0100
    Re: python function parameters, debugging, comments, etc. Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-10-02 11:15 +0100
      Re: python function parameters, debugging, comments, etc. Rotwang <sg552@hotmail.co.uk> - 2013-10-02 14:52 +0100

csiph-web