<div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 25, 2018 at 10:10 PM Lee Braiden <<a href="mailto:leebraid@gmail.com">leebraid@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span style="font-size:12.8px;font-family:sans-serif">It's the reason why type checking exists, and why bounds checking exists, and why unit checking exists too.</span></div></blockquote><div dir="auto"><br></div><div dir="auto">And yet Python has none of those. They all provide safety, but also place a burden on the developer.</div><div dir="auto"><br></div><div dir="auto">So why use Python? I’m not arguing that all those features don’t have their advantages, but I am wondering why add them all to Python, rather than using a language designed for safety?</div><div dir="auto"><br></div><div dir="auto">But Python has such a great ecosystem of packages! Yes, it does — but you might ask yourself why that is.</div><div dir="auto"><br></div><div dir="auto">All that being said — do go and make a nice DbC package for Python — maybe all us naysayers will grow to love it!</div><div dir="auto"><br></div><div dir="auto">But could we please stop cluttering this list with discussion of how great or not great it is?</div><div dir="auto"><br></div><div dir="auto">These meta-conversations are getting really tiresome.</div><div dir="auto"><br></div><div dir="auto">-CHB</div><div dir="auto"><br></div><div dir="auto"><br></div></div></div>-- <br><div dir="ltr" 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>