Message344677
> Regarding your comment on client_context.num_ticket getter: IMHO it's not a good idea to raise an exception on attribute access. It may break introspection.
Hmm, I see what you mean.
Basically my intuition is: it's a bit weird to make the attribute's existence "sort of" depend on whether it's a client or server context. It would make sense to me to have it entirely disappear on client contexts (from __dir__, read-access, and write-access), and it would make sense to me to have it always be present, just a no-op. But having it present, and almost the same as on server contexts, except that assigning to it fails... that feels a little weird. |
|
Date |
User |
Action |
Args |
2019-06-05 06:33:51 | njs | set | recipients:
+ njs, janssen, christian.heimes, alex, dstufft |
2019-06-05 06:33:51 | njs | set | messageid: <1559716431.43.0.172380615907.issue37120@roundup.psfhosted.org> |
2019-06-05 06:33:51 | njs | link | issue37120 messages |
2019-06-05 06:33:51 | njs | create | |
|