Files
feedBack-desktop/scripts
cf3c19a503 fix(build/runtime): isolate bundled Python from the build/user site-packages
Two related fixes for the bundled embeddable/standalone Python:

- build-common.sh exports PYTHONNOUSERSITE=1 for the whole build. Without it,
  pip on a dev/CI machine that has a system Python sees transitive deps as
  'already satisfied' via the per-user site (~/.local, %APPDATA%\Python) and
  SKIPS bundling them (typing_extensions, urllib3, certifi, ...). The packaged
  app then crashes with ModuleNotFoundError on clean end-user machines while
  'working' on the build box. Clean CI runners have no user site, so this is a
  no-op there.
- python.ts sets PYTHONNOUSERSITE=1 in the spawned server env so a stray
  user-site package on an end-user machine can't shadow (or mask a gap in) the
  bundled deps. When packaged it also sets SLOPSMITH_SKIP_PLUGIN_INSTALL=1 so
  the server doesn't block startup doing runtime 'pip install' of heavy
  optional plugin deps (torch/whisperx/demucs) — that hung the backend past the
  readiness window on first launch. (Pairs with the slopsmith core change that
  honours that flag.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-18 00:25:09 -07:00
..
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00
2026-06-16 18:48:12 +02:00