Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

74,737

Downloads of v 1.2.4:

87

Last Update:

04 Dec 2019

Package Maintainer(s):

Software Author(s):

  • Kiran Kumar Kotari

Tags:

python virtual environment pyenv

pyenv-win

Downloads:

74,737

Downloads of v 1.2.4:

87

Maintainer(s):

Software Author(s):

  • Kiran Kumar Kotari

pyenv-win

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
WARNING

This package was rejected on 21 Jan 2020. The reviewer chocolatey-ops has listed the following reason(s):

bazzilic (maintainer) on 21 Nov 2019 07:27:54 +00:00:

User 'bazzilic' (maintainer) submitted package.

chocolatey-ops (reviewer) on 21 Nov 2019 08:01:39 +00:00:

pyenv-win has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Title (title) matches id exactly. Please consider using something slightly more descriptive for the title in the nuspec. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 21 Nov 2019 12:05:22 +00:00:

pyenv-win has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/6ce0f634f87799ddc45152fa9ea49604 for details.
This is an FYI only. There is no action you need to take.

Pauby (reviewer) on 04 Dec 2019 05:58:59 +00:00:

Hi, a couple of issues / suggestions / questions:

  1. You are modifying the path in your chocolateyInstall.ps1 but not removing those modifications in the chocolateyUninstall.ps1. Can you add that?
  2. Can you provide step by step instructions in the VERIFICATION.txt file on how to verify the checksum for the embedded file?

Thanks.

bazzilic (maintainer) on 04 Dec 2019 06:08:49 +00:00:

Hello Pauby,

  1. AFAIK, Chocolatey doesn't support that now (see https://github.com/chocolatey/choco/issues/310)
  2. Ok, updated verification.txt

bazzilic (maintainer) on 04 Dec 2019 06:10:05 +00:00:

User 'bazzilic' (maintainer) submitted package.

bazzilic (maintainer) on 04 Dec 2019 06:11:24 +00:00:

User 'bazzilic' (maintainer) submitted package.

bazzilic (maintainer) on 04 Dec 2019 06:12:24 +00:00:

User 'bazzilic' (maintainer) submitted package.

bazzilic (maintainer) on 04 Dec 2019 06:13:26 +00:00:

Well, I can't push the updated version now, it says:

"An error has occurred. It's possible the package version already exists on the repository."

bazzilic (maintainer) on 04 Dec 2019 06:14:25 +00:00:

Or maybe I did push.. I don't even know.

chocolatey-ops (reviewer) on 04 Dec 2019 06:47:29 +00:00:

pyenv-win has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Title (title) matches id exactly. Please consider using something slightly more descriptive for the title in the nuspec. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 04 Dec 2019 06:52:43 +00:00:

pyenv-win has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/11be9a44e417a71dc1d249070830741e for details.
This is an FYI only. There is no action you need to take.

Pauby (reviewer) on 04 Dec 2019 08:17:58 +00:00:

Hi,

> AFAIK, Chocolatey doesn't support that now (see https://github.com/chocolatey/choco/issues/310)

Chocolatey doesn't have a helper to do this, you're correct. But that doesn't mean you should clean up the environment after you uninstall the package. You will need to write the PowerShell code around that to have it removed.

If you're changing the environment, you need to undo those changes on uninstall.

Thanks.

bazzilic (maintainer) on 09 Dec 2019 05:06:32 +00:00:

I'd like to have a second opinion on that. I would argue that it is better not to manually cleanup $path during uninstall. Other than to OCD, there is no harm in having dead paths in $path; however, there is always a possibility of screwing something up when altering the variable contents. Imo, unless Chocolatey provides a way to cleanup whatever was added there during install, package uninstallers should just leave it as is.

Pauby (reviewer) on 17 Dec 2019 16:47:42 +00:00:

I appreciate your comments however you need to cleanup the environment after your package is uninstalled. Many packages make the same changes you make and also undo those changes on uninstall.

Unfortunately unless the changes are made we cannot proceed with the package.

chocolatey-ops (reviewer) on 06 Jan 2020 16:51:20 +00:00:

We've found pyenv-win v1.2.4 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 21 Jan 2020 16:54:02 +00:00:

Unfortunately there has not been progress to move pyenv-win v1.2.4 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

pyenv is a simple python version management tool. It lets you easily switch between multiple versions of Python. It's simple, unobtrusive, and follows the UNIX tradition of single-purpose tools that do one thing well.


tools\chocolateyInstall.ps1
Install-ChocolateyZipPackage `
    -PackageName 'pyenv-win' `
    -UnzipLocation "$env:USERPROFILE\.pyenv\" `
    -File "$(Split-Path -parent $MyInvocation.MyCommand.Definition)/pyenv-win.zip" `
    -ChecksumType "sha256" `
    -Checksum "3CEAE64ECE3A0340B16DBA5B6914DA5163AAA6EA1149A76078CF8C53E7153762"

Install-ChocolateyPath `
    -PathToInstall "$env:USERPROFILE\.pyenv\pyenv-win\bin"

Install-ChocolateyPath `
    -PathToInstall "$env:USERPROFILE\.pyenv\pyenv-win\shims"
    
tools\chocolateyUninstall.ps1
Uninstall-ChocolateyZipPackage `
    -PackageName "pyenv-win" `
    -ZipFileName "pyenv-win.zip"
tools\LICENSE.txt
MIT License

Copyright (c) 2019 Kiran Kumar Kotari

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\pyenv-win.zip
md5: 0B0D6A525D73CD4A567C1122F132CFF7 | sha1: 969E057F4A65DB832B31F9F3F68459B8A22A93DF | sha256: 3CEAE64ECE3A0340B16DBA5B6914DA5163AAA6EA1149A76078CF8C53E7153762 | sha512: 8550FF5489FF1CADD111065060E401D57666F6797C6524963EDD456B76DB5CB7FF13E6661E92A6F30679431A458BE59143BE949A6D414A737E91BCEA97D21178
tools\VERIFICATION.txt
To obtain the files for this Chocolatey package do the following:

1. Install git
2. Run:   git clone https://github.com/pyenv-win/pyenv-win.git
3. In PowerShell run:   Compress-Archive -Path "pyenv-win/*" -DestinationPath "./pyenv-win.zip" -CompressionLevel Optimal -Force
4. File "pyenv-win.zip" should be identical to the one in the package

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
pyenv-win 2.64.11 21591 Thursday, September 16, 2021 Approved
pyenv-win 2.64.10 1204 Wednesday, September 1, 2021 Approved
pyenv-win 2.64.9 2992 Monday, July 12, 2021 Approved
pyenv-win 2.64.8 1547 Tuesday, June 15, 2021 Approved
pyenv-win 2.64.7.4 1428 Friday, May 28, 2021 Approved
pyenv-win 2.64.3 10019 Monday, September 7, 2020 Approved
pyenv-win 2.64.1 353 Tuesday, August 4, 2020 Approved
pyenv-win 1.2.4.20200707 1035 Tuesday, July 7, 2020 Approved
pyenv-win 1.2.4.20200318 1867 Wednesday, March 18, 2020 Approved
pyenv-win 0.0.132 817 Tuesday, November 5, 2019 Approved

This package has no dependencies.

Discussion for the pyenv-win Package

Ground Rules:

  • This discussion is only about pyenv-win and the pyenv-win package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or pyenv-win, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus