Message182671
| Author |
r.david.murray |
| Recipients |
demian.brecht, r.david.murray |
| Date |
2013年02月22日.16:19:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1361549971.4.0.217400444935.issue17272@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
One of those other options is: do nothing :)
Python doesn't normally make things read-only just because mutating them does nothing useful. Sometimes we make things read-only when mutating them does nasty stuff, but even then sometimes we don't.
So the real question is, do others consider it a sensible and useful API change to make setting it do something useful, and how many other changes would be required to make the rest of the API consistent with that change?
We may be in python-ideas territory here, I'm not sure. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年02月22日 16:19:31 | r.david.murray | set | recipients:
+ r.david.murray, demian.brecht |
| 2013年02月22日 16:19:31 | r.david.murray | set | messageid: <1361549971.4.0.217400444935.issue17272@psf.upfronthosting.co.za> |
| 2013年02月22日 16:19:31 | r.david.murray | link | issue17272 messages |
| 2013年02月22日 16:19:31 | r.david.murray | create |
|