Message10006

Jeff, so our convention has been to update the APIVersion for any bytecode change that results in different behavior - including especially bug fixes. I think we still need to do this with subsequent releases in 2.7.x, especially since we want to open up opportunities for future optimization around generated bytecode.

Te specific ImportError message could be more nuanced, however. In cases like this I especially favor helpful diagnostic messages vs something terse.