Despite changing the path with additions to sys.path, any class within the btm.pyt file don't retain these changes -- apparently the underlying calling environment only knows how to see static imports and not our dynamic importing mechanism, and can be confused then if other items collide on the path, which is not uncommon for things like utils.
To fix this, force our scripts directory into the path in each function -- a hack, but will work for the time being till we can file an issue on the ArcPy side.
Despite changing the path with additions to
sys.path, anyclasswithin thebtm.pytfile don't retain these changes -- apparently the underlying calling environment only knows how to see static imports and not our dynamic importing mechanism, and can be confused then if other items collide on the path, which is not uncommon for things likeutils.To fix this, force our scripts directory into the path in each function -- a hack, but will work for the time being till we can file an issue on the ArcPy side.