I think it would be good to report where the error happens. The idea of lazy_import objects is that their location is rebound to the actual object before serious use. That obviously doesn't happen here, so it's probably a mis-imported lazyimport object. This happen when you, for instance, do
from <module> import lazily_imported_object
The truth is: the LazyImport wrappers are probably good enough for wrapping functions, but are provably not sufficient for wrapping whole objects (on which you call __div__). So in my opiniion, the fact that you find a lazyimport object on which __div__ is called, is a bug.