microsoft / microsoft/winget-pkgs
[Package Issue]: Python.PythonInstallManager MSIX lacks a scope
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- PR merge metrics
- PR metrics pending
Description
### Please confirm these before moving forward
- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.
### Category of the issue
Other
### Brief description of your issue
When checking the Python.PythonInstallManager install options, the MSIX version lacks a scope declaration (is it machine, is it user?). I would assume it's meant to be user scope judging by MSIX.
### Steps to reproduce
This was based on an inspection in Robopack, but it can be seen there is no scope declaration in the source file.
### Actual behavior
Scope is empty.
### Expected behavior
A scope is expected.
### Environment
```raw
N/A
```
### Screenshots and Logs
https://github.com/microsoft/winget-pkgs/blob/master/manifests/p/Python/PythonInstallManager/26.0.240.0/Python.PythonInstallManager.installer.yaml (file for ref that the MSI has a scope, but the MSIX does not)
Contributor guide
Research direction
Open manifests/p/Python/PythonInstallManager/26.0.240.0/Python.PythonInstallManager.installer.yaml and compare the MSIX installer entry with the MSI entry that declares a scope. Add the missing MSIX scope using the intended value, then confirm the manifest shows a non-empty scope for both installer types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100