<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 9 Aug 2012, at 22:24, Luc Bourhis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 9 Aug 2012, at 19:39, Nathaniel Echols wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I actually think introducing -Qnew was a mistake, because there are<br>third-party modules [...] which simply break when true division<br>is forced. [...] I definitely</blockquote><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Sans'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">agree that it would be better if everyone continues to use the<br>explicit division styles instead of relying on the Python<br>interpreter's default behavior</span></blockquote><br></div><div>I agree with you that using -Qnew has annoying side-effects. However I beg to differ as to the best solution. Imho we should enforce</div><div>from __future__ import division</div><div>at the beginning of every single Python module by adding another diagnostic to libtbx.find_clutter.</div></div></blockquote><br></div><div>Moreover, I should add that I have the opposite problem. I need to integrate cctbx-based code into Bruker's Python code that is run without -Qnew. The only easy way is to add the __future__ line.</div><div><br></div><div>Luc</div><div><br></div></body></html>