You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow LOAD to accept an absolute or relative path to a .neug_extension binary, in addition to the current name-based lookup under $NEUG_EXTENSION_HOME_PYENV/extension/<name>/.
import neug also overwrites NEUG_EXTENSION_HOME_PYENV to the wheel/site-packages tree. So a separately built out-of-tree artifact is not found unless the user:
copies/symlinks into the pip extension directory, or
overrides NEUG_EXTENSION_HOME_PYENV after import to point at the extension build root
Both work, but are awkward for local development. Path-based LOAD is the natural fix.
Summary
Allow
LOADto accept an absolute or relative path to a.neug_extensionbinary, in addition to the current name-based lookup under$NEUG_EXTENSION_HOME_PYENV/extension/<name>/.This unblocks the common out-of-tree workflow:
NEUG_EXTENSION_CONFIGS/neug_extension_load(see feat: support out-of-tree extensions via NEUG_EXTENSION_CONFIGS #745)pip install neug(or another NeuG build)site-packagesMotivation
Today
load_extensionalways treats the argument as an extension name and resolves:import neugalso overwritesNEUG_EXTENSION_HOME_PYENVto the wheel/site-packages tree. So a separately built out-of-tree artifact is not found unless the user:NEUG_EXTENSION_HOME_PYENVafter import to point at the extension build rootBoth work, but are awkward for local development. Path-based
LOADis the natural fix.Proposed usage
Name-based
LOAD wigglestays unchanged for installed / CI-packaged extensions.