On 9 Aug 2012, at 22:24, Luc Bourhis wrote:
On 9 Aug 2012, at 19:39, Nathaniel Echols wrote:
I actually think introducing -Qnew was a mistake, because there are third-party modules [...] which simply break when true division is forced. [...] I definitely agree that it would be better if everyone continues to use the explicit division styles instead of relying on the Python interpreter's default behavior
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 from __future__ import division at the beginning of every single Python module by adding another diagnostic to libtbx.find_clutter.
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. Luc