Message280892
That presumably means adding special None support to all the places None can appear in a message, where now the code treats None like it does every other object. I'm not sure the added complexity is worth it, especially since NoneType would still creep in anywhere we'd forgotten to "fix". I'm not voting -1, but I'm dubious.
Maybe we should just make NoneType's name be 'None' :) |
|
Date |
User |
Action |
Args |
2016-11-15 20:43:19 | r.david.murray | set | recipients:
+ r.david.murray, brett.cannon, gward |
2016-11-15 20:43:19 | r.david.murray | set | messageid: <1479242599.55.0.879056619014.issue28702@psf.upfronthosting.co.za> |
2016-11-15 20:43:19 | r.david.murray | link | issue28702 messages |
2016-11-15 20:43:19 | r.david.murray | create | |
|