<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 3, 2017 at 11:15 AM, Kyle Lahnakoski <span dir="ltr"><<a href="mailto:klahnakoski@mozilla.com" target="_blank">klahnakoski@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Python<br>
has a fundamentally different philosophy about None that conflicts with<br>
what I need for my domain [2] where I am transforming and interpreting<br>
data. Using a set of classes that make a different set of assumptions<br>
about None is not arduous, it keeps the definitions separate, and I<br>
still get all wonderfulness of Python.<br></blockquote><div><br></div><div>not really related to this thread, but you may want to use your own "sentinal" singletons, rather than special case code to deal with None.</div><div><br></div><div>i.e.</div><div><br></div><div>BadData</div><div>MissingData</div><div>UnSpecified</div><div><br></div><div>M.A. Lemberg has been talking about that on this list (in this thread? I've lost track...)</div><div><br></div><div>-CHB</div><div><br></div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div></div>