Added
- Open Folder and New Instance in the mini window. The cockpit has no menu
bar and no file tree, so switching project used to mean restoring the full
window first. Two new icons sit left of Run: an open-folder glyph and a
second-window glyph, both drawn in the active theme like the rest of the bar. - Opening a folder opens its entry point. KhervePY now looks in the project
root formain.py, then for a script named after the folder itself
(KherveStats/KherveStats.py), and opens the first one it finds — so Run
works immediately after Open, which is the whole point of the cockpit. If
neither exists the status line says so instead of leaving Run pointing at
nothing. In the mini window, where the status bar is hidden, that message goes
to the Output panel.
Fixed (0.38.1, first released here)
- Run works in the installed build again. Windows keeps a 0-byte
python.exein%LOCALAPPDATA%\Microsoft\WindowsApps— an "app execution
alias" whose only job is to open the Microsoft Store — and that directory sits
near the front ofPATH. Interpreter discovery took the firstpythonon
PATH, so the frozen KhervePY (which has no interpreter of its own to fall
back on) always handedQProcessthe placeholder, and every Run died with
could not start the interpreter. - Discovery now walks
PATHin full and skips those stubs, then falls back to
the interpreters registered underSOFTWARE\Python\PythonCoreand to the
standard install directories (…\Programs\Python\Python3*,
C:\Program Files\Python3*,C:\Python3*), newest first. A real install is
found even when it was never added toPATH. - If a stub is genuinely the only thing on the machine, Run still reports the
failure — but now explains that the path is a Store placeholder and how to fix
it.
Downloads: KhervePY-Setup-0.39.0.exe (installer) or
KhervePY-0.39.0-windows.zip (portable). The installer is unsigned, so
SmartScreen will warn — choose More info → Run anyway.