Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gregory Ewing Newsgroups: comp.lang.python Subject: Re: None versus MISSING sentinel -- request for design feedback Date: Sat, 16 Jul 2011 14:24:21 +1200 Lines: 13 Message-ID: <98cb2oF3vpU1@mid.individual.net> References: <4e1fd009$0$29986$c3e8da3$5496439d@news.astraweb.com> <4e201a9d$0$29989$c3e8da3$5496439d@news.astraweb.com> <4e203706$0$29972$c3e8da3$5496439d@news.astraweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net i2CXfKQPVzZ9FClGz7Gs1gt5cGAq7R3dW/BAye37oj4/k3p9nA Cancel-Lock: sha1:PhaKPI7kAp+LvuuJT1aa/gCuP34= User-Agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711) X-Accept-Language: en-us, en In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:9591 Ethan Furman wrote: > some > of the return values (Logical, Date, DateTime, and probably Character) > will have their own dedicated singletons (Null, NullDate, NullDateTime, > NullChar -- which will all compare equal to None) That doesn't seem like a good idea to me. It's common practice to use 'is' rather than '==' when comparing things to None. Why do you want to use special null values for these types? -- Greg