Message113698
| Author | daniel.urban |
|---|---|
| Recipients | daniel.urban, pitrou, terry.reedy, thet |
| Date | 2010-08-12.18:52:21 |
| SpamBayes Score | 2.2725085e-06 |
| Marked as misclassified | No |
| Message-id | <1281639143.15.0.141345697454.issue5996@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think, that the reason is that, object.__new__ checks, if the class is instantiable (object_new in Objects/typeobject.c ). dict.__new__ (and tuple.__new__, and I guess the __new__ method of other built-in types) doesn't call object.__new__, but user defined types typically either doesn't have a __new__, or call object.__new__ from it (directly or with super). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-08-12 18:52:23 | daniel.urban | set | recipients: + daniel.urban, terry.reedy, pitrou, thet |
| 2010-08-12 18:52:23 | daniel.urban | set | messageid: <1281639143.15.0.141345697454.issue5996@psf.upfronthosting.co.za> |
| 2010-08-12 18:52:21 | daniel.urban | link | issue5996 messages |
| 2010-08-12 18:52:21 | daniel.urban | create | |