Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[New Feature]: make Python.Launcher branched #135072

Closed
soredake opened this issue Jan 16, 2024 · 2 comments
Closed

[New Feature]: make Python.Launcher branched #135072

soredake opened this issue Jan 16, 2024 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone
1.7 Packages

Comments

@soredake
Copy link
Contributor

Description of the new feature/enhancement

Right now Python.Launcher package does not have branches, which results in this situation where winget wants to update python.launcher to latest version (3.12) even when you installed python ≤3.11, this should not happen:
image

To reproduce:

winget install -h --id=Python.Python.3.11  -e
winget upgrade

Proposed technical implementation details (optional)

No response
@soredake soredake added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 16, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 16, 2024
@stephengillie stephengillie removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 17, 2024
@stephengillie
Copy link
Collaborator

Is Python.Launcher meant to have different versions installed side-by-side? For instance, with 3.12 installed, should installing 3.11 result in both 3.11 and 3.12 installed and independently usable?

@soredake
Copy link
Contributor Author

Is Python.Launcher meant to have different versions installed side-by-side?

My bad, it is not, and turns out python.launcher is backwards compatible, closing.

@soredake soredake closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2024
@denelon denelon added this to the 1.7 Packages milestone Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
None yet
Milestone
1.7 Packages
Development

No branches or pull requests
3 participants
@soredake @denelon @stephengillie