On Wed, Jan 8, 2014 at 4:00 PM, James Stroud <xtald00d@gmail.com> wrote:

> /usr/bin/python /path/to/libtbx/configure.py --old_division cctbx
>
> which will give you cleaner dispatchers. I'm pretty sure the rest of CCTBX should still behave sensibly, since we're pretty militant about including the __future__ statement in these files. Is that sufficiently usable for the short term?

That works fine for a developer, but it doesn’t help much with users, who shouldn’t be expected to create a custom build of CCTBX.

True - but our assumption (possibly incorrect) has been that there aren't many people downloading binary builds of CCTBX and then combining them with other Python modules. The majority of CCTBX "users", as far as I know, are either people actively developing code based on or within CCTBX, or the end users of Phenix, CCP4, etc.

Attached is a tar file (fixit.tar) of three python scripts that should solve this problem easily:

All of the code in CCTBX is already patched (I just fixed the one or two recent additions that weren't). The problem is all of the code in Phenix, which we would like to ensure has consistent behavior - this was the primary reason for adding "-Qnew". The maintenance overhead is already enormous and I don't have either the time or authority to micromanage my collaborators. (Nor does anyone else, for that matter.) In this case I think the current behavior is risky enough to justify a one-time intervention, but I'm not going to do anything without first discussing it with the Powers That Be.

-Nat