This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients brett.cannon, gward, r.david.murray
Date 2016-11-15.20:43:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479242599.55.0.879056619014.issue28702@psf.upfronthosting.co.za>
In-reply-to
Content
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' :)
History
Date User Action Args
2016-11-15 20:43:19r.david.murraysetrecipients: + r.david.murray, brett.cannon, gward
2016-11-15 20:43:19r.david.murraysetmessageid: <1479242599.55.0.879056619014.issue28702@psf.upfronthosting.co.za>
2016-11-15 20:43:19r.david.murraylinkissue28702 messages
2016-11-15 20:43:19r.david.murraycreate