Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #65143 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2014-01-31 12:57 -0800 |
| Last post | 2014-01-31 12:57 -0800 |
| 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: __init__ is the initialiser Ethan Furman <ethan@stoneleaf.us> - 2014-01-31 12:57 -0800
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2014-01-31 12:57 -0800 |
| Subject | Re: __init__ is the initialiser |
| Message-ID | <mailman.6223.1391204795.18130.python-list@python.org> |
On 01/31/2014 12:48 PM, MRAB wrote: > On 2014-01-31 19:52, Ned Batchelder wrote: >> >> Why can't we call __init__ the constructor and __new__ the allocator? > > The advantage of calling it the "initialiser" is that it explains why > it's called "__init__". Hm, yes, good point. Also, __init__ initializes so it is a good choice. Ignore the names comment in my previous post. -- ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web