Message175497
| Author | skrah |
|---|---|
| Recipients | eric.araujo, eric.snow, ezio.melotti, georg.brandl, gvanrossum, mrabarnett, py.user, serhiy.storchaka, skrah, vstinner |
| Date | 2012-11-13.11:06:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1352804780.03.0.624099324197.issue14260@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not so sure. If dicts or classes are used for configuration or informational purposes, I prefer them to be locked down. An example of the first is the decimal context, where it was possible to write context.emax = 9 instead of context.Emax = 9 without getting an error. This is an easy mistake to make and can be hard to track down in a large program. The mistake here is maybe less likely, but I agree with Georg that it's a case for a read-only dict/dictproxy. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-11-13 11:06:20 | skrah | set | recipients: + skrah, gvanrossum, georg.brandl, vstinner, ezio.melotti, eric.araujo, mrabarnett, py.user, eric.snow, serhiy.storchaka |
| 2012-11-13 11:06:20 | skrah | set | messageid: <1352804780.03.0.624099324197.issue14260@psf.upfronthosting.co.za> |
| 2012-11-13 11:06:19 | skrah | link | issue14260 messages |
| 2012-11-13 11:06:19 | skrah | create | |