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- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
pyenv-win
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
74,737
Downloads of v 1.2.4:
87
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
DetailsScan 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.
This package was rejected on 21 Jan 2020. The reviewer chocolatey-ops has listed the following reason(s):
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.
Uninstall-ChocolateyZipPackage `
-PackageName "pyenv-win" `
-ZipFileName "pyenv-win.zip"
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.
md5: 0B0D6A525D73CD4A567C1122F132CFF7 | sha1: 969E057F4A65DB832B31F9F3F68459B8A22A93DF | sha256: 3CEAE64ECE3A0340B16DBA5B6914DA5163AAA6EA1149A76078CF8C53E7153762 | sha512: 8550FF5489FF1CADD111065060E401D57666F6797C6524963EDD456B76DB5CB7FF13E6661E92A6F30679431A458BE59143BE949A6D414A737E91BCEA97D21178
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.
- pyenv-winInstall.zip (9cd62d418902) - ## / 60
- pyenv-win.1.2.4.nupkg (4fcc39b1fe78) - ## / 62
- pyenv-winInstall.zip (3ceae64ece3a) - ## / 61
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 3.1.1 | 31603 | Saturday, September 3, 2022 | Approved | |
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.
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.
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.
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.
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:
Thanks.
bazzilic (maintainer) on 04 Dec 2019 06:08:49 +00:00:
Hello Pauby,
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.
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.
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:
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'.