microsoft / microsoft/winget-pkgs

Package: PyEnv

Open
#17,988 15 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Issue-Feature Package-Request
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Package Requested

  • I would like someone else to build the manifest.
  • I would like help so I can submit the manifest.
  • I have performed a search and couldn't find this package.
  • I think there is a new version available and I have provided the URL.

Manifest:

Fill out as much of the manifest metadata you can:

PackageIdentifier:  PyEnv.PyEnv # publisher.package format (example: "Microsoft.WindowsTerminal")
PackageVersion:     2.0.1.0 # version number format x.y.z.a (example: "1.6.10571.0")
PackageLocale:      en-US # meta-data locale (example: "en-US")
Publisher:          PyEnv # publisher name (example: "Microsoft Corporation")
PackageName:        PyEnv   # package name (example: "Windows Terminal")
License:            MIT # package license (example: "MIT")
ShortDescription:   Simple Python version management # package description (example: "The new Windows Terminal")
Installers: 
 - Architecture:     / # installer architecture (example: "x64")
   InstallerType:    Source Code + Path variable # installer type (example: "msix")
   InstallerUrl:     https://github.com/pyenv/pyenv/releases/tag/v2.0.1 # installer URL (should be https://)
   InstallerSha256:  /# SHA256 hash calculated from installer
ManifestType: singleton
ManifestVersion: 1.0.0

Note: This was started but never finished? https://github.com/pyenv-win/pyenv-win/issues/134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the requested PyEnv metadata and the linked pyenv-win issue #134. Check the repository's manifest schema and comparable package manifests before validating the package details and installer information. Done means a complete, valid manifest can be submitted for PyEnv.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.