Dev guide: modernize Python install guidance for shell developers - #23
Merged
Merged
Conversation
The dev-env page told developers to install Python 3.9.x (EOL Oct 2025) and carried pip-version guidance from the 2.7 era; the getting-started page used a Python27 path example. Now: install a current 64-bit Python 3 (shellfoundry supports 3.9-3.13; 3.13 needs shellfoundry 1.2.29+), with an explicit note that shells still EXECUTE on the Python bundled with CloudShell (3.9.9 / 2.7.18), so driver code must stay compatible with that. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nahumtimerman
added a commit
that referenced
this pull request
Sep 10, 2026
…inputs, category validation (#24) Documents the three behavior-changing items that landed on 2026.1 after the 2026.1.0.52 pass (#18) and were not covered by #19-#22. Python 3 upgraded to 3.13.15 x64 (Trunk CS 189988/189997/189999, backported in CS 190003). This is the WINDOWS bundled slot only - the Docker ES image still builds Python 3.9.9, and so do the Linux VA and the from-script ES, so every page states the platform split rather than a blanket "CloudShell now uses 3.13". Python 2.7.18 is untouched. Also corrects setting-up-dev-env.md, which #23 had just updated to say the bundled version is 3.9.9 - true when it merged on Sep 6, wrong when the upgrade landed on Sep 8. Global inputs kept on save as blueprint, with the new KeepResourceGlobalInputsOnSaveAsBlueprint key (CS 189903/189905/189914). Default is true, which is a behavior change on upgrade: inputs that fronted a resource requirement used to be dropped and are now visible in the Reserve dialog and the blueprint editor. Documented as a customer-visible key on the Server (AppSettingVisibility.Customer, read by ServiceConfigSettingsLoader). Blueprint import now fails on a category missing from the target domain instead of silently dropping the association (CS 189942). The ExportBlueprint/ImportBlueprint page from #22 already stated this, so it needed no correction - only the release notes did. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Customer-reported: the dev guide still instructs installing Python 3.9.x (EOL Oct 2025) — and shellfoundry appeared to "rely on older Python".
With shellfoundry 1.2.29 (QualiSystems/shellfoundry#276) and cloudshell-rest-api 9.0.2 (QualiSystems/cloudshell-rest-api#32, #33) now live on PyPI, developers can use Python 3.9–3.13 on their dev machines.
Changes:
C:\Python27\ScriptsPATH example withC:\Python313\Scripts.Deliberately not touched: platform system-requirements pages (third-party-software etc.) — those correctly describe what the platform bundles today and change only with the platform Python upgrade.
🤖 Generated with Claude Code