Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #64039 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-01-16 12:46 +1100 |
| Last post | 2014-01-16 12:46 +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.
Re: data validation when creating an object Chris Angelico <rosuav@gmail.com> - 2014-01-16 12:46 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-01-16 12:46 +1100 |
| Subject | Re: data validation when creating an object |
| Message-ID | <mailman.5561.1389836816.18130.python-list@python.org> |
On Thu, Jan 16, 2014 at 12:25 PM, Cameron Simpson <cs@zip.com.au> wrote:
> However, I would also have obvious validity checks in __init__
> itself on the supplied values. Eg:
>
> def __init__(self, size, lifetime):
> if size < 1:
> raise ValueError("size must be >= 1, received: %r" % (size,))
> if lifetime <= 0:
> raise ValueError("lifetime must be > 0, received: %r" % (lifetime,))
>
> Trivial, fast. Fails early. Note that the exception reports the
> receive value; very handy for simple errors like passing utterly
> the wrong thing (eg a filename when you wanted a counter, or something
> like that).
With code like this, passing a filename as the size will raise TypeError on Py3:
>>> size = "test.txt"
>>> size < 1
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: unorderable types: str() < int()
Yet another advantage of Py3 :)
ChrisA
Back to top | Article view | comp.lang.python
csiph-web