Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: joshua.landau.ws@gmail.com
In-Reply-To: <185a0a88-9515-43e6-ae65-73d86b0299e7@googlegroups.com>
References: <185a0a88-9515-43e6-ae65-73d86b0299e7@googlegroups.com>
From: Joshua Landau <joshua@landau.ws>
Date: Sat, 17 Aug 2013 15:38:17 +0100
Subject: Re: Check for the type of arguments
To: Fernando Saldanha <fsaldan1@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.15.1376750347.23369.python-list@python.org>
Lines: 55
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:52629

On 17 August 2013 13:34, Fernando Saldanha <fsaldan1@gmail.com> wrote:
> I am new to Python, with some experience in Java, C++ and R.
>
> Writing in other languages I usually check the type and values of functio=
n arguments. In the Python code examples I have seen this is rarely done.
>
> Questions:
>
> 1) Is this because it would be "unpythonic" or just because the examples =
are not really production code?

Unpythonic. Python duck-types so we tend to take things as long as the
seem like they work. This is really helpful if you want to provide a
custom type or data object to a function (or anything really). If it
looks like a duck and quacks like a duck... you can probably make a
duck sandwich.

> 2) If I still want to check the type of my arguments, do I
>
> a) use type() or is instance() to check for type?

You'd want to travel down this stack, choosing the first reasonable one:

=E2=80=A2 Don't check at all

=E2=80=A2 Check that it can do what you need it to do, such as by calling
"iter(input)" to check that it's iterable.

=E2=80=A2 Check using an ABC (http://docs.python.org/3/library/abc.html) wi=
th isinstance

=E2=80=A2 Check that it has the methods you need using hasattr

=E2=80=A2 Check using "isinstance(...)" against a type

=E2=80=A2 Check using "type(...) is"

The choices higher up are better than the choices lower down.

> b) use assert (I guess not),

"assert" is for things that *can't* be wrong (yet still sometimes
are). Don't normally assert user input, I'd say.

>raise a ValueError,

Sounds right.

>or sys.exit()?

No. You should never be throwing a SystemExit except at top-level.

> (I noticed that raising a ValueError does not stop execution when I am ru=
nning the Interactive Interpreter under PTVS, which I find inconvenient, bu=
t it does stop execution when running the code non-interactively.)