Release Pyxle Language Tools 0.3.1 - #14
Merged
Merged
Conversation
Closes the Unreleased section: the dev server is no longer interrupted seconds after it starts, both debug configurations run the selected interpreter, a stale editable install is no longer mistaken for an old one, and the interpreter is visible and switchable from a .pyxl file. A patch rather than a minor: the release exists to fix behaviour that 0.3.0 shipped broken, and the new status-bar item and Select Interpreter command are part of that fix — interpreter selection was unreachable from a .pyxl editor, which is what made the version errors a dead end.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.3.1 from what is already on
main: bumps the manifest and turns the CHANGELOG's Unreleased section into the release heading.What ships
^Cfirst to interrupt whatever is running — killing the freshly started server. The extension owns the process now, so nothing else can write to it.pyxlecame first onPATH, not VS Code's selected interpreter..pyxlfile (status-bar item + Pyxle: Select Python Interpreter), which is what made the version errors a dead end before.taskkillfailure that could throw and strand the process tree on Windows, exit settling before stdio drained (printing "stopped" above the traceback), a deadonDidExitthat cost a 120 s silent lockout when a server died on startup, a missing discovery re-check after the interpreter gate, and an over-claiming changelog line.Patch, not minor — this exists to fix behaviour 0.3.0 shipped broken; the new status-bar affordance is part of that fix rather than a separate feature.
Verified:
tsc --noEmitclean, 23/23 tests, andvsce packageproduces a clean 12-file / 110 KB .vsix carrying"version": "0.3.1"with no source, tests, tsconfigs ornode_modulesleaking in.