If I am developing an ST package and need a custom (or 3rd-party) Python package to go with it, by looking at some of the existing ST packages, it LOOKS like the correct way to do that is to include the Python package in a subdirectory below the ST package root, and to make it “look” like a Python package by having a __init__.py
file in there. Then importing uses the standard Python package “pathing”. Example:
<st_data>/Packages/MyPackage/my_python_lib_dir/__init__.py
…and other Python package files there. Then
from .my_python_lib_dir import module_name
Is this the correct (ST-designer-intended) way to do it?
(I looked and didn’t find any other Forum topics on this, nor have I found any documentation on it.)