Message156792
| Author | gvanrossum |
|---|---|
| Recipients | Jim.Jewett, eric.snow, gvanrossum, r.david.murray, rhettinger, vstinner |
| Date | 2012-03-26.00:23:38 |
| SpamBayes Score | 9.341798e-10 |
| Marked as misclassified | No |
| Message-id | <1332721419.83.0.00802917880461.issue14386@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Given that dictproxy is needed to implement the proper interface for classes I don't think it is an implementation detail, and so I think it ought to be constructable. We have more esoteric types constructable (e.g. function). I also happen to think that its use to implement classes is a pretty darn good use case, and I am sure there are other use cases. I don't really care if we make it a builtin but there should be a standard name for it somewhere in the stdlib. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-03-26 00:23:40 | gvanrossum | set | recipients: + gvanrossum, rhettinger, vstinner, r.david.murray, eric.snow, Jim.Jewett |
| 2012-03-26 00:23:39 | gvanrossum | set | messageid: <1332721419.83.0.00802917880461.issue14386@psf.upfronthosting.co.za> |
| 2012-03-26 00:23:39 | gvanrossum | link | issue14386 messages |
| 2012-03-26 00:23:38 | gvanrossum | create | |