community.chocolatey.org
Open in
urlscan Pro
2606:4700::6812:154c
Public Scan
Submitted URL: https://chocolatey.org/packages/python
Effective URL: https://community.chocolatey.org/packages/python
Submission: On August 02 via api from DE — Scanned from CA
Effective URL: https://community.chocolatey.org/packages/python
Submission: On August 02 via api from DE — Scanned from CA
Form analysis 4 forms found in the DOM
GET /packages
<form class="search-box" autocomplete="off" role="search" action="/packages" method="get" style="opacity: 1;">
<div class="flex-grow-1 position-relative">
<div class="autoComplete_wrapper" role="combobox" aria-owns="autoComplete_list_1" aria-haspopup="true" aria-expanded="false"><input id="autoComplete" class="search-input" name="q" inputmode="search" type="search" dir="ltr" spellcheck="false"
autocorrect="off" autocomplete="off" autocapitalize="off" value="" aria-controls="autoComplete_list_1" aria-autocomplete="both" placeholder="Search packages or get suggestions...">
<ul id="autoComplete_list_1" role="listbox" hidden=""></ul>
</div>
<i class="fa-solid fa-magnifying-glass" aria-hidden="true"></i>
<span class="d-none d-md-block search-key-container">
<kbd class="search-key">ctrl</kbd>
<kbd>k</kbd>
</span>
</div>
<button type="button" aria-label="Close search" class="btn btn-search-close btn-outline-primary ms-2"><i class="fa-solid fa-xmark" aria-hidden="true"></i></button>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" method="post">
<fieldset>
<input name="__RequestVerificationToken" type="hidden" value="9IvfH/zvpkAjLBAiZ1NKNuRgN4iA9oiRbuQJGgrNVudTbhT5D/GlgWjbIqZZ+qNzeruUYv10bQUC5EGbjnFN83D0JfLR7270xBZ0ul2vDCGVURm70rgHny58I/yMRbpWe389aIdiXS/1+ViHTtNFxrl7bzhPGJ1o00kCpPWlUlc=">
<button class="btn link-theme m-0 p-0" type="submit"><i class="fa-solid fa-right-from-bracket fa-flip-horizontal text-primary w-px-15 text-center me-3"></i>Sign Out</button>
</fieldset>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" class="w-100 user-authenticated" method="post">
<fieldset class="nav-link">
<input name="__RequestVerificationToken" type="hidden" value="HNNPIPq0JItxIM5g3bQnOjOyyGTr447im3hGgCZ+H0++rBH4KdUSJJldueCSamExuahySHOEm2jmD5JM0MHGR+jOMRzyPzTdwTX/Gvfzh1+GkHeBceH5crcXsJUntoj3vlofDpek06rDPd5D0Utnd+f4xLIqPoAuHKiWtyx/2Fc=">
<button class="btn link-theme m-0 p-0" type="submit">Sign Out</button>
</fieldset>
</form>Name: mc-embedded-subscribe-form — POST //chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d
<form action="//chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate="">
<div class="row align-items-center justify-content-center">
<div class="col-md-auto text-center text-md-start">
<h3 class="mb-0">Signup for the Newsletter!</h3>
</div>
<div class="col-md-3">
<input type="email" title="Email Address for Newsletter" class="form-control email mt-2 mt-md-0" id="mce-EMAIL" placeholder="Your e-mail address" value="" name="EMAIL" required="">
</div>
<div style="position: absolute; left: -5000px;">
<input title="Invisible Field" type="text" name="b_86a6d80146a0da7f2223712e4_73b018498d" tabindex="-1" value="">
</div>
<div class="col-md-auto">
<button type="submit" class="btn btn-bg-body mt-2 mt-md-0 w-100" id="mc-embedded-subscribe"><strong>Subscribe</strong></button>
</div>
</div>
<p class="mb-0 mt-1 text-center"><i>Be the first to know about upcoming features, security releases, and news about Chocolatey.</i></p>
</form>Text Content
1
RESOURCES
Watch videos, read documentation, and hear Chocolatey success stories from
companies you trust.
View Resources
EVENTS
Find past and upcoming webinars, workshops, and conferences. New events have
recently been added!
View Events
COURSES
Step-by-step guides for all things Chocolatey! Earn badges as you learn through
interactive digital courses.
View Courses
--------------------------------------------------------------------------------
Join our monthly Unpacking Software livestream to hear about the latest news,
chat and opinion on packaging, software deployment and lifecycle management!
Learn More
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
Don't miss a byte of Chocolatey goodness! Explore our livestream events now!
* Main
* Community
* Docs
* Blog
* Install
* * Light
* Dark
* Auto
* Light
* Dark
* Auto
1
ctrl k
* * Main
* Community
* Docs
* Blog
* Install
* * Light
* Dark
* Auto
* Packages
* Learn
* Resources
* Courses
* Product
Products
* Chocolatey for Business
* Pro Edition
* Chocolatey Open Source
* Compare Editions
* Pricing
* Support
Solutions
* Self-Service Anywhere
* Central Management Deployments
* Secure Offline Deployments
Ready to give Chocolatey for Business a Try?
We offer a 14 day white glove free trial to help get you started.
Start Trial
* Connect
* Events
* Careers
* Newsletter
* Chocolatey Community
* Support
* Contact
*
*
*
*
*
*
*
*
*
* Bluesky butterfly logo
*
* --------------------------------------------------------------------------------
* Sign In
* Sign Up
* * Profile
* Account
* --------------------------------------------------------------------------------
* Sign Out
* Profile
* Account
* Sign Out
Welcome to the Chocolatey Community Package Repository! The packages found in
this section of the site are provided, maintained, and moderated by the
community.
MODERATION
Every version of each package undergoes a rigorous moderation process before it
goes live that typically includes:
* Security, consistency, and quality checking
* Installation testing
* Virus checking through VirusTotal
* Human moderators who give final review and sign off
More detail at Security and Moderation.
ORGANIZATIONAL USE
If you are an organization using Chocolatey, we want your experience to be fully
reliable. Due to the nature of this publicly offered repository, reliability
cannot be guaranteed. Packages offered here are subject to distribution rights,
which means they may need to reach out further to the internet to the official
locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition
of Chocolatey (including the free open source edition), you can host your own
packages and cache or internalize existing community packages.
DISCLAIMER
Your use of the packages on this site means you understand they are not
supported or guaranteed in any way. Learn more...
I Understand
Generate Script
0 B U I L D E R
* STEP1
Package Review
* STEP2
Integration Method
* STEP3
Install Script / Config
* STEP4
Environment Setup
* STEP5
Install Script
Previous Next
STEP 1: REVIEW YOUR PACKAGES
STEP 2: CHOOSE YOUR INTEGRATION METHOD
* Generic
* Individual
* Ansible
*
* PS DSC
*
STEP 3: ENTER YOUR INTERNAL REPOSITORY URL
(this should look similar to https://community.chocolatey.org/api/v2/)
STEP 3: COPY YOUR SCRIPT OR DOWNLOAD CONFIG
OPTION 1: COPY SCRIPT
OPTION 2: DOWNLOAD CONFIG
Save as .config File
STEP 4: SETUP YOUR ENVIRONMENT
1. ENSURE YOU ARE SET FOR ORGANIZATIONAL DEPLOYMENT
Please see the organizational deployment guide
2. GET THE PACKAGE INTO YOUR ENVIRONMENT
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)
* Open Source or Commercial:
* Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory
Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to
https://community.chocolatey.org/api/v2/. Packages cache on first access
automatically. Make sure your choco clients are using your proxy repository
as a source and NOT the default community repository. See source command
for more information.
* You can also just download the packages and push them to a repository
Download Packages
Option 2: Internalized Package (Reliable, Scalable)
* Open Source
* Download the packages:
Download Packages
* Follow manual internalization instructions
* Package Internalizer (C4B)
* Run: (additional options)
* For package and dependencies run:
* Automate package internalization
STEP 5: COPY YOUR SCRIPT
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places
where you are calling directly to Chocolatey. If you are integrating, keep in
mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes
are shown as failures:
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"
#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
#### We use this variable for future REST calls.
$RequestArguments = @{
UseBasicParsing = $true
}
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "http://internal/odata/repo"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.3.0.nupkg"
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
$TempDirectory = Join-Path $env:Temp "chocolateyInstall"
if (-not (Test-Path $TempDirectory -PathType Container)) {
$null = New-Item -Path $TempDirectory -ItemType Directory
}
$DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments
#### Extract the Nupkg, and run the chocolateyInstall script
if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
} else {
# PowerShell versions <4.0 do not have this function available
try {
$shellApplication = New-Object -ComObject Shell.Application
$zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
$destinationFolder = $shellApplication.NameSpace($TempDirectory)
$destinationFolder.CopyHere($zipPackage.Items(), 0x10)
} catch {
Write-Warning "Unable to unzip package using built-in compression."
throw $_
}
}
& $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
refreshenv
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400
#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress
### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
choco source remove -n $_.Name
}
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco source disable --name chocolatey.licensed
} else {
Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
if ($ChocolateyCentralManagementClientSalt) {
choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
}
if ($ChocolateyCentralManagementServiceSalt) {
choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
}
choco feature enable --name useChocolateyCentralManagement
choco feature enable --name useChocolateyCentralManagementDeployments
}
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy
- name: Install and Configure Chocolatey
hosts: all
## 2. TOP LEVEL VARIABLES ##
vars:
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
nuget_repository_url: http://internal/odata/repo
### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
# nuget_repository_username: username
# nuget_repository_password: password
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService
#### ii. If using a Client Salt, add it here
# chocolatey_central_management_client_salt: clientsalt
#### iii. If using a Service Salt, add it here
# chocolatey_central_management_service_salt: servicesalt
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
tasks:
- name: Install chocolatey
win_chocolatey:
name: chocolatey
source: ""{{ nuget_repository_url }}""
# source_username: ""{{ nuget_repository_username }}""
# source_password: ""{{ nuget_repository_password }}""
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# - name: Enable FIPS compliance
# win_chocolatey_feature:
# name: useFipsCompliantChecksums
# state: enabled
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
- name: Set the cache location
win_chocolatey_config:
name: cacheLocation
state: present
value: C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
- name: Set the command execution timeout
win_chocolatey_config:
name: commandExecutionTimeoutSeconds
state: present
value: 14400
#### Turn off download progress when running choco through integrations
- name: Disable showing download progress
win_chocolatey_feature:
name: showDownloadProgress
state: disabled
### c. Sources ###
#### Remove the default community package repository source
- name: Remove Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey
state: absent
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
- name: Add Internal Repository
win_chocolatey_source:
name: ChocolateyInternal
state: present
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
priority: 1
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
- name: Upgrade Chocolatey
win_chocolatey:
name: chocolatey
state: latest
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
- name: Install Chocolatey License
win_chocolatey:
name: chocolatey-license
source: ChocolateyInternal
state: latest
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
- name: Disable Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey.licensed
state: disabled
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
- name: Install Chocolatey Extension
win_chocolatey:
name: chocolatey.extension
source: ChocolateyInternal
state: latest
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
- name: Hide not-elevated warnings
win_chocolatey_feature:
name: showNonElevatedWarnings
state: disabled
- name: Use background mode for self-service
win_chocolatey_feature:
name: useBackgroundService
state: enabled
- name: Use background service for non-admins
win_chocolatey_feature:
name: useBackgroundServiceWithNonAdministratorsOnly
state: enabled
- name: Allow background uninstallation for user installs
win_chocolatey_feature:
name: allowBackgroundServiceUninstallsFromUserInstallsOnly
state: enabled
- name: Set allowed background service commands
win_chocolatey_config:
name: backgroundServiceAllowedCommands
state: present
value: install,upgrade,uninstall
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
- name: Install Chocolatey Agent
when: chocolatey_central_management_url is defined
win_chocolatey:
name: chocolatey-agent
source: ChocolateyInternal
state: latest
- name: Set the Central Management Service URL
when: chocolatey_central_management_url is defined
win_chocolatey_config:
name: CentralManagementServiceUrl
state: present
value: {{ chocolatey_central_management_url }}
- name: Set the Central Management Client Salt
when: chocolatey_central_management_client_salt is defined
win_chocolatey_config:
name: centralManagementClientCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_client_salt }}
- name: Set the Central Management Service Salt
when: chocolatey_central_management_service_salt is defined
win_chocolatey_config:
name: centralManagementServiceCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_service_salt }}
- name: Use Central Management
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagement
state: enabled
- name: Use Central Management Deployments
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagementDeployments
state: enabled
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "http://internal/odata/repo"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "http://internal/odata/repo/package/chocolatey.2.3.0.nupkg",
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
# action :enable
# end
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
value 'C:\ProgramData\chocolatey\cache'
end
#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
value '14400'
end
#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
action :disable
end
### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
action :remove
end
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
source "#{NugetRepositoryUrl}"
priority 1
action :add
end
execute 'ChocolateyInternal' do
command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
action :upgrade
source "#{NugetRepositoryUrl}"
end
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
action :install
source "#{NugetRepositoryUrl}"
end
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
action :disable
end
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
action install
source "#{NugetRepositoryUrl}"
end
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
action :disable
end
chocolatey_feature 'useBackgroundService' do
action :enable
end
chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
action :enable
end
chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
action :enable
end
chocolatey_config 'backgroundServiceAllowedCommands' do
value 'install,upgrade,uninstall'
end
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
action install
source "#{NugetRepositoryUrl}"
# user "#{NugetRepositoryUsername}"
# password "#{NugetRepositoryPassword}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'CentralManagementServiceUrl' do
value "#{ChocolateyCentralManagementUrl}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementClientSalt}"
only_if { ChocolateyCentralManagementClientSalt != nil }
end
chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementServiceSalt}"
only_if { ChocolateyCentralManagementServiceSalt != nil }
end
chocolatey_feature 'useChocolateyCentralManagement' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_feature 'useChocolateyCentralManagementDeployments' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
$null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
}
Install-Module -Name cChoco
if ($PSGallery.InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
}
}
#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1
Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
param(
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "http://internal/odata/repo",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "http://internal/odata/repo/package/chocolatey.2.3.0.nupkg",
### c. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# ),
### d. Install.ps1 URL
#### The path to the hosted install script:
$ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"
### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt",
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Import-DscResource -ModuleName cChoco
Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
Environment chocoDownloadUrl {
Name = "chocolateyDownloadUrl"
Value = $ChocolateyNupkgUrl
}
cChocoInstaller installChocolatey {
DependsOn = "[Environment]chocoDownloadUrl"
InstallDir = Join-Path $env:ProgramData "chocolatey"
ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# cChocoFeature featureFipsCompliance {
# FeatureName = "useFipsCompliantChecksums"
# }
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
cChocoConfig cacheLocation {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "cacheLocation"
Value = "C:\ProgramData\chocolatey\cache"
}
#### Increase timeout to at least 4 hours
cChocoConfig commandExecutionTimeoutSeconds {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "commandExecutionTimeoutSeconds"
Value = 14400
}
#### Turn off download progress when running choco through integrations
cChocoFeature showDownloadProgress {
DependsOn = "[cChocoInstaller]installChocolatey"
FeatureName = "showDownloadProgress"
Ensure = "Absent"
}
### c. Sources ###
#### Remove the default community package repository source
cChocoSource removeCommunityRepository {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "chocolatey"
Ensure = "Absent"
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
cChocoSource addInternalSource {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "ChocolateyInternal"
Source = $NugetRepositoryUrl
Credentials = $NugetRepositoryCredential
Priority = 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
cChocoPackageInstaller updateChocolatey {
DependsOn = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
Name = "chocolatey"
AutoUpgrade = $true
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
cChocoPackageInstaller chocolateyLicense {
DependsOn = "[cChocoPackageInstaller]updateChocolatey"
Name = "chocolatey-license"
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
Script disableLicensedSource {
DependsOn = "[cChocoPackageInstaller]chocolateyLicense"
GetScript = {
$Source = choco source list --limitoutput | `
ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
Where-Object Name -eq "chocolatey.licensed"
return @{
Result = if ($Source) {
[bool]::Parse($Source.Disabled)
} else {
Write-Warning "Source 'chocolatey.licensed' was not present."
$true # Source does not need disabling
}
}
}
SetScript = {
$null = choco source disable --name "chocolatey.licensed"
}
TestScript = {
$State = [ScriptBlock]::Create($GetScript).Invoke()
return $State.Result
}
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
cChocoPackageInstaller chocolateyLicensedExtension {
DependsOn = "[Script]disableLicensedSource"
Name = "chocolatey.extension"
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
cChocoFeature hideElevatedWarnings {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "showNonElevatedWarnings"
Ensure = "Absent"
}
cChocoFeature useBackgroundService {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundService"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceWithNonAdmins {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
Ensure = "Present"
}
cChocoConfig allowedBackgroundServiceCommands {
DependsOn = "[cChocoFeature]useBackgroundService"
ConfigName = "backgroundServiceAllowedCommands"
Value = "install,upgrade,uninstall"
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
cChocoPackageInstaller chocolateyAgent {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
Name = "chocolatey-agent"
}
cChocoConfig centralManagementServiceUrl {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "CentralManagementServiceUrl"
Value = $ChocolateyCentralManagementUrl
}
if ($ChocolateyCentralManagementClientSalt) {
cChocoConfig centralManagementClientSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementClientSalt
}
}
if ($ChocolateyCentralManagementServiceSalt) {
cChocoConfig centralManagementServiceSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementServiceSalt
}
}
cChocoFeature useCentralManagement {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagement"
Ensure = "Present"
}
cChocoFeature useCentralManagementDeployments {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagementDeployments"
Ensure = "Present"
}
}
}
}
# If working this into an existing configuration with a good method for
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
}
)
}
try {
Push-Location $env:Temp
$Config = ChocolateyConfig -ConfigurationData $ConfigData
Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
Pop-Location
}
Copy
Requires Puppet Chocolatey Provider module. See docs at
https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
#### See https://forge.puppet.com/puppetlabs/chocolatey
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'http://internal/odata/repo'
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'http://internal/odata/repo/package/chocolatey.2.3.0.nupkg'
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'
#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
### source locations. This is directly to the bare download url for the
### chocolatey.nupkg, similar to what you see when you browse to
### https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
chocolatey_download_url => $_choco_download_url,
use_7zip => false,
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#chocolateyfeature {'useFipsCompliantChecksums':
# ensure => enabled,
#}
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
value => 'C:\ProgramData\chocolatey\cache',
}
#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
value => '14400',
}
#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
ensure => disabled,
}
### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
ensure => absent,
location => 'https://community.chocolatey.org/api/v2/',
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
ensure => present,
location => $_repository_url,
priority => 1,
username => 'optional',
password => 'optional,not ensured',
bypass_proxy => true,
admin_only => false,
allow_self_service => false,
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
package {'chocolatey':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license
# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
ensure => disabled,
priority => '10',
user => 'customer',
password => '1234',
require => Package['chocolatey-license'],
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
ensure => disabled,
}
chocolateyfeature {'useBackgroundService':
ensure => enabled,
}
chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
ensure => enabled,
}
chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
ensure => enabled,
}
chocolateyconfig {'backgroundServiceAllowedCommands':
value => 'install,upgrade,uninstall',
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
package {'chocolatey-agent':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
chocolateyconfig {'CentralManagementServiceUrl':
value => $_chocolatey_central_management_url,
}
if $_chocolatey_central_management_client_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
if $_chocolatey_central_management_service_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
chocolateyfeature {'useChocolateyCentralManagement':
ensure => enabled,
require => Package['chocolatey-agent'],
}
chocolateyfeature {'useChocolateyCentralManagementDeployments':
ensure => enabled,
require => Package['chocolatey-agent'],
}
}
Copy
Previous Next
Need Help? View our docs or file an issue.
THERE IS ALREADY A VERSION OF THIS PACKAGE IN YOUR SCRIPT BUILDER
Current Version New Version
Delete and Add New Version Cancel
Downloads:
24,989,057
Downloads of v 3.13.0-rc1:
91
Last Update:
01 AUG 2024
Package Maintainer(s):
* chocolatey-community
Software Author(s):
* Python Software Foundation
Tags:
python programming development foss cross-platform admin
* Software Specific:
* Software Site
* Software Source
* Software License
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
PYTHON
This is a prerelease version of Python.
* 1
* 2
* 3
3.13.0-rc1 | Updated: 01 Aug 2024
Show Additional Links
* Software Specific:
* Software Site
* Software Source
* Software License
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
Downloads:
24,989,057
Downloads of v 3.13.0-rc1:
91
Maintainer(s):
* chocolatey-community
Software Author(s):
* Python Software Foundation
Tags:
python programming development foss cross-platform admin
PYTHON 3.13.0-RC1
This is a prerelease version of Python.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are
affiliated with or endorsed by Python Software Foundation. The inclusion of
Python Software Foundation trademark(s), if any, upon this webpage is solely to
identify Python Software Foundation goods or services and not for commercial
purposes.
* 1
* 2
* 3
THIS PACKAGE CONTAINS AN EXEMPTED CHECK
Not All Tests Have Passed
Hide Checks
Hide Checks
--------------------------------------------------------------------------------
Validation Testing Passed
--------------------------------------------------------------------------------
Verification Testing Exemption:
Python3 is bypassing verifier, so this package will need to as well.
Details
--------------------------------------------------------------------------------
Scan Testing Successful:
No detections found in any package files
Details
*
*
* Generic
* Individual
* Ansible
*
* PS DSC
*
Add to Script Builder Learn More
--------------------------------------------------------------------------------
DEPLOYMENT METHOD: INDIVIDUAL INSTALL, UPGRADE, & UNINSTALL
* Install
* Upgrade
* Uninstall
To install Python, run the following command from the command line or from
PowerShell:
>
To upgrade Python, run the following command from the command line or from
PowerShell:
>
To uninstall Python, run the following command from the command line or from
PowerShell:
>
DEPLOYMENT METHOD:
NOTE
This applies to both open source and commercial editions of Chocolatey.
1. ENTER YOUR INTERNAL REPOSITORY URL
(this should look similar to https://community.chocolatey.org/api/v2/)
--------------------------------------------------------------------------------
2. SETUP YOUR ENVIRONMENT
1. ENSURE YOU ARE SET FOR ORGANIZATIONAL DEPLOYMENT
Please see the organizational deployment guide
2. GET THE PACKAGE INTO YOUR ENVIRONMENT
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)
* Open Source or Commercial:
* Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory
Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to
https://community.chocolatey.org/api/v2/. Packages cache on first access
automatically. Make sure your choco clients are using your proxy repository
as a source and NOT the default community repository. See source command
for more information.
* You can also just download the package and push it to a repository Download
Option 2: Internalized Package (Reliable, Scalable)
* Open Source
* Download the package:
Download
* Follow manual internalization instructions
* Package Internalizer (C4B)
* Run: (additional options)
choco download python --internalize --pre --source=https://community.chocolatey.org/api/v2/
Copy
* For package and dependencies run:
You must enter your internal repository url above before proceeding.
choco push --source="'http://internal/odata/repo'"
Copy
* Automate package internalization
--------------------------------------------------------------------------------
3. COPY YOUR SCRIPT
You must enter your internal repository url above before proceeding.
choco upgrade python -y --source="'http://internal/odata/repo'" --prerelease [other options]
Copy
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places
where you are calling directly to Chocolatey. If you are integrating, keep in
mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes
are shown as failures:
You must enter your internal repository url above before proceeding.
choco upgrade python -y --source="'http://internal/odata/repo'" --prerelease
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
Copy
You must enter your internal repository url above before proceeding.
- name: Install python
win_chocolatey:
name: python
version: '3.13.0-rc1'
source: http://internal/odata/repo
state: present
allow_prerelease: yes
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
You must enter your internal repository url above before proceeding.
chocolatey_package 'python' do
action :install
source 'http://internal/odata/repo'
version '3.13.0-rc1'
options '--prerelease'
end
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
You must enter your internal repository url above before proceeding.
cChocoPackageInstaller python
{
Name = "python"
Version = "3.13.0-rc1"
Source = "http://internal/odata/repo"
chocoParams = "--prerelease"
}
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
You must enter your internal repository url above before proceeding.
package { 'python':
ensure => '3.13.0-rc1',
install_options => ['--prerelease'],
provider => 'chocolatey',
source => 'http://internal/odata/repo',
}
Copy
Requires Puppet Chocolatey Provider module. See docs at
https://forge.puppet.com/puppetlabs/chocolatey.
--------------------------------------------------------------------------------
4. IF APPLICABLE - CHOCOLATEY CONFIGURATION/INSTALLATION
See infrastructure management matrix for Chocolatey configuration elements and
examples.
Package Approved
This package was approved as a trusted package on 01 Aug 2024.
Description
--------------------------------------------------------------------------------
Python is a programming language that lets you work more quickly and integrate
your systems more effectively. You can learn to use Python and see almost
immediate gains in productivity and lower maintenance costs.
NOTES
* This package depends on the the latest major version of python package.
* This package do not support package parameters, please install the package
python313 directly when using package parameters.
* If the package is out of date please check Version History for the latest
submitted version. If you have a question, please ask it in Chocolatey
Community Package Discussions or raise an issue on the Chocolatey Community
Packages Repository if you have problems with the package. Disqus comments
will generally not be responded to.
Files
--------------------------------------------------------------------------------
Virus Scan Results
--------------------------------------------------------------------------------
Log in or click on link to see number of positives.
* python.3.13.0-rc1.nupkg (fa706213c1ff) - ## / 67
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.
Version History
Add to Builder Version Downloads Last Updated Status Python 3.13.0-rc1 91
Thursday, August 1, 2024 Approved Python 3.13.0-b4 548 Friday, July 19, 2024
Approved Python 3.13.0-b3 813 Sunday, June 30, 2024 Approved Python 3.13.0-b2
748 Friday, June 7, 2024 Approved Python 3.13.0-b1 933 Friday, May 10, 2024
Approved Python 3.13.0-a6 855 Thursday, April 11, 2024 Approved Python 3.13.0-a5
856 Friday, March 15, 2024 Approved Python 3.13.0-a4 956 Saturday, February 17,
2024 Approved Python 3.13.0-a3 943 Saturday, January 20, 2024 Approved Python
3.13.0-a2 1708 Friday, November 24, 2023 Approved Python 3.13.0-a1 1518
Saturday, October 14, 2023 Approved Python 3.12.4 748201 Friday, June 7, 2024
Approved Python 3.12.3 851678 Tuesday, April 9, 2024 Approved Python 3.12.2
889254 Wednesday, February 7, 2024 Approved Python 3.12.1 811721 Friday,
December 8, 2023 Approved Python 3.12.0 922450 Monday, October 2, 2023 Approved
Python 3.12.0-rc3 644 Tuesday, September 19, 2023 Approved Python 3.12.0-rc2 600
Wednesday, September 6, 2023 Approved Python 3.12.0-rc1 1194 Sunday, August 6,
2023 Approved Python 3.12.0-b4 993 Wednesday, July 12, 2023 Approved Python
3.12.0-b3 1021 Wednesday, June 21, 2023 Approved Python 3.12.0-b2 588 Wednesday,
June 7, 2023 Approved Python 3.12.0-b1 570 Wednesday, May 24, 2023 Approved
Python 3.12.0-a7 209 Wednesday, April 5, 2023 Approved Python 3.12.0-a6 914
Wednesday, March 22, 2023 Approved Python 3.12.0-a2 4661 Thursday, November 17,
2022 Approved Python 3.12.0-a1 969 Tuesday, October 25, 2022 Approved Python
3.11.9 9039 Tuesday, April 2, 2024 Approved Python 3.11.8 3941 Wednesday,
February 7, 2024 Approved Python 3.11.7 3147 Tuesday, December 5, 2023 Approved
Python 3.11.6 7971 Monday, October 2, 2023 Approved Python 3.11.5 540591
Thursday, August 24, 2023 Approved Python 3.11.4 1028063 Wednesday, June 7, 2023
Approved Python 3.11.3 854024 Wednesday, April 12, 2023 Approved Python 3.11.2
317627 Wednesday, March 22, 2023 Approved Python 3.11.0 2032609 Tuesday, October
25, 2022 Approved Python 3.11.0-rc2 1710 Monday, September 12, 2022 Approved
Python 3.11.0-rc1 1301 Monday, August 8, 2022 Approved Python 3.11.0-b5 567
Tuesday, July 26, 2022 Approved Python 3.11.0-b4 876 Tuesday, July 12, 2022
Approved Python 3.11.0-b3 1323 Wednesday, June 1, 2022 Approved Python 3.11.0-b2
210 Tuesday, May 31, 2022 Approved Python 3.11.0-b1 779 Sunday, May 8, 2022
Approved Python 3.11.0-a7 1012 Wednesday, April 6, 2022 Approved Python
3.11.0-a6 923 Tuesday, March 8, 2022 Approved Python 3.11.0-a5 996 Saturday,
February 5, 2022 Approved Python 3.11.0-a4 714 Monday, January 17, 2022 Approved
Python 3.11.0-a3 1073 Thursday, December 9, 2021 Approved Python 3.11.0-a2 885
Saturday, November 6, 2021 Approved Python 3.11.0-a1 854 Thursday, October 7,
2021 Approved Python 3.10.11 22690 Thursday, April 6, 2023 Approved Python
3.10.10 6998 Wednesday, March 22, 2023 Approved Python 3.10.8 194232 Wednesday,
October 12, 2022 Approved Python 3.10.7 488250 Tuesday, September 6, 2022
Approved Python 3.10.6 458168 Tuesday, August 2, 2022 Approved Python 3.10.5
707023 Monday, June 6, 2022 Approved Python 3.10.4 931350 Thursday, March 24,
2022 Approved Python 3.10.3 130364 Wednesday, March 16, 2022 Approved Python
3.10.2 1962861 Monday, January 17, 2022 Approved Python 3.10.1 531550 Tuesday,
December 7, 2021 Approved Python 3.10.0 863986 Tuesday, October 5, 2021 Approved
Python 3.10.0-rc2 736 Wednesday, September 8, 2021 Approved Python 3.10.0-rc1
812 Tuesday, August 3, 2021 Approved Python 3.10.0-b4 673 Sunday, July 11, 2021
Approved Python 3.10.0-b3 561 Friday, June 18, 2021 Approved Python 3.10.0-b2
507 Tuesday, June 1, 2021 Approved Python 3.10.0-b1 627 Tuesday, May 4, 2021
Approved Python 3.10.0-a7 740 Wednesday, April 7, 2021 Approved Python 3.10.0-a6
883 Tuesday, March 2, 2021 Approved Python 3.10.0-a5 816 Wednesday, February 3,
2021 Approved Python 3.10.0-a4 842 Tuesday, January 5, 2021 Approved Python
3.10.0-a3 605 Tuesday, December 8, 2020 Approved Python 3.10.0-a2 839 Tuesday,
November 3, 2020 Approved Python 3.10.0-a1 902 Tuesday, October 6, 2020 Approved
Python 3.9.13 109307 Tuesday, May 17, 2022 Approved Python 3.9.12 23163
Thursday, March 24, 2022 Approved Python 3.9.11 2191 Wednesday, March 16, 2022
Approved Python 3.9.10 7456 Monday, January 17, 2022 Approved Python 3.9.9 13202
Tuesday, November 16, 2021 Approved Python 3.9.8 1488 Saturday, November 6, 2021
Approved Python 3.9.7 435221 Tuesday, August 31, 2021 Approved Python 3.9.6
818008 Tuesday, June 29, 2021 Approved Python 3.9.5 674514 Tuesday, May 4, 2021
Approved Python 3.9.4 318591 Monday, April 5, 2021 Approved Python 3.9.2 492884
Friday, February 19, 2021 Approved Python 3.9.1 763790 Tuesday, December 8, 2020
Approved Python 3.9.0 744868 Monday, October 5, 2020 Approved Python 3.9.0-rc2
588 Thursday, September 17, 2020 Approved Python 3.9.0-rc1 950 Wednesday, August
12, 2020 Approved Python 3.9.0-b5 779 Tuesday, July 21, 2020 Approved Python
3.9.0-b4 610 Friday, July 3, 2020 Approved Python 3.9.0-b3 713 Wednesday, June
10, 2020 Approved Python 3.9.0-b2 305 Tuesday, June 9, 2020 Approved Python
3.9.0-b1 581 Tuesday, May 19, 2020 Approved Python 3.9.0-a6 620 Tuesday, April
28, 2020 Approved Python 3.9.0-a5 877 Tuesday, March 24, 2020 Approved Python
3.9.0-a4 765 Wednesday, February 26, 2020 Approved Python 3.9.0-a3 890 Saturday,
January 25, 2020 Approved Python 3.9.0-a2-20200110 559 Friday, January 10, 2020
Approved Python 3.9.0-a2 599 Thursday, December 19, 2019 Approved Python
3.9.0-a1 788 Wednesday, November 20, 2019 Approved Python 3.8.10 79396 Monday,
May 3, 2021 Approved Python 3.8.9 23787 Friday, April 2, 2021 Approved Python
3.8.8 23484 Friday, February 19, 2021 Approved Python 3.8.7 5702 Tuesday,
December 22, 2020 Approved Python 3.8.6 121247 Thursday, September 24, 2020
Approved Python 3.8.6-rc1 235 Wednesday, September 9, 2020 Approved Python
3.8.5.20200721 546202 Tuesday, July 21, 2020 Approved Python 3.8.5 793130
Monday, July 20, 2020 Approved Python 3.8.4 66993 Tuesday, July 14, 2020
Approved Python 3.8.4-rc1 261 Friday, July 3, 2020 Approved Python 3.8.3 620990
Thursday, May 14, 2020 Approved Python 3.8.3-rc1 233 Thursday, April 30, 2020
Approved Python 3.8.2 458457 Wednesday, February 26, 2020 Approved Python
3.8.1.20200110 117324 Friday, January 10, 2020 Approved Python 3.8.1 30883
Thursday, December 19, 2019 Approved Python 3.8.0 229393 Tuesday, October 15,
2019 Approved Python 3.8.0-rc1 446 Wednesday, October 2, 2019 Approved Python
3.8.0-b4 889 Friday, August 30, 2019 Approved Python 3.8.0-b3 686 Tuesday, July
30, 2019 Approved Python 3.8.0-b2 549 Friday, July 5, 2019 Approved Python
3.8.0-b1 720 Wednesday, June 5, 2019 Approved Python 3.8.0-a4 650 Tuesday, May
7, 2019 Approved Python 3.8.0-a3 771 Tuesday, March 26, 2019 Approved Python
3.8.0-a2 581 Tuesday, February 26, 2019 Approved Python 3.8.0-a1 545 Monday,
February 4, 2019 Approved Python 3.7.9 60493 Tuesday, August 18, 2020 Approved
Python 3.7.8 10385 Sunday, June 28, 2020 Approved Python 3.7.7 19822 Tuesday,
March 10, 2020 Approved Python 3.7.6.20200110 1010 Friday, January 10, 2020
Approved Python 3.7.6 323679 Thursday, December 19, 2019 Approved Python 3.7.5
60195 Wednesday, October 16, 2019 Approved Python 3.7.4 189034 Tuesday, July 9,
2019 Approved Python 3.7.3 91104 Tuesday, March 26, 2019 Approved Python 3.7.2
92850 Monday, December 24, 2018 Approved Python 3.7.2-rc1 446 Wednesday,
December 12, 2018 Approved Python 3.7.1 38432 Saturday, October 20, 2018
Approved Python 3.7.1-rc2 422 Sunday, October 14, 2018 Approved Python 3.7.1-rc1
478 Thursday, September 27, 2018 Approved Python 3.7.0 171422 Thursday, June 28,
2018 Approved Python 3.7.0-rc1 523 Wednesday, June 13, 2018 Approved Python
3.7.0-b5 506 Thursday, May 31, 2018 Approved Python 3.7.0-b4 629 Thursday, May
3, 2018 Approved Python 3.7.0-b3 621 Friday, March 30, 2018 Approved Python
3.7.0-b2 672 Wednesday, February 28, 2018 Approved Python 3.7.0-b1 717 Thursday,
February 1, 2018 Approved Python 3.7.0-a4-20180116 570 Tuesday, January 16, 2018
Approved Python 3.7.0-a4 581 Tuesday, January 9, 2018 Approved Python 3.7.0-a3
672 Wednesday, December 6, 2017 Approved Python 3.7.0-a2 645 Thursday, November
9, 2017 Approved Python 3.6.8.20200110 400 Friday, January 10, 2020 Approved
Python 3.6.8 165521 Monday, December 24, 2018 Approved Python 3.6.8-rc1 296
Wednesday, December 12, 2018 Approved Python 3.6.7 35218 Saturday, October 20,
2018 Approved Python 3.6.7-rc2 316 Sunday, October 14, 2018 Approved Python
3.6.7-rc1 337 Thursday, September 27, 2018 Approved Python 3.6.6 73488 Thursday,
June 28, 2018 Approved Python 3.6.6-rc1 385 Wednesday, June 13, 2018 Approved
Python 3.6.5 75192 Thursday, March 29, 2018 Approved Python 3.6.5-rc1 410
Wednesday, March 14, 2018 Approved Python 3.6.4.20180116 27941 Tuesday, January
16, 2018 Approved Python 3.6.4 13526 Tuesday, December 19, 2017 Approved Python
3.6.4-rc1 499 Wednesday, December 6, 2017 Approved Python 3.6.3 207679
Wednesday, October 4, 2017 Approved Python 3.6.2 22995 Monday, July 17, 2017
Approved Python 3.6.1 25569 Wednesday, March 22, 2017 Approved Python 3.6.0
30313 Friday, December 23, 2016 Approved Python 3.5.4.20200110 1235 Friday,
January 10, 2020 Approved Python 3.5.4 35721 Thursday, November 9, 2017 Approved
Python 3.5.2.20161029 12465 Saturday, October 29, 2016 Approved Python
3.5.1.20161002 5968 Sunday, October 2, 2016 Approved Python 3.5.1 30217 Sunday,
December 27, 2015 Approved Python 3.4.4.20200110 2692 Friday, January 10, 2020
Approved Python 3.4.4.20180111 8552 Thursday, January 11, 2018 Approved Python
3.4.4 1497 Thursday, November 9, 2017 Approved Python 3.4.3.20150501 20136
Friday, May 1, 2015 Approved Python 3.4.3 7996 Wednesday, February 25, 2015
Approved Python 3.4.2 12293 Wednesday, October 8, 2014 Approved Python
3.4.1.20141004 968 Saturday, October 4, 2014 Approved Python 3.4.1.20140610 5742
Tuesday, June 10, 2014 Approved Python 3.4.1 914 Saturday, June 7, 2014 Approved
Python 3.4.0.20140321 3950 Tuesday, March 25, 2014 Approved Python 3.4.0 1813
Monday, March 17, 2014 Approved Python 3.3.5.20200110 225 Friday, January 10,
2020 Approved Python 3.3.5 387 Tuesday, February 26, 2019 Approved Python 3.3.4
987 Thursday, November 9, 2017 Approved Python 3.2.5.20200110 227 Friday,
January 10, 2020 Approved Python 3.2.5 597 Thursday, November 9, 2017 Approved
Python 3.1.4.20200110 223 Friday, January 10, 2020 Approved Python 3.1.4 497
Thursday, November 9, 2017 Approved Python 3.0.1.20200110 239 Friday, January
10, 2020 Approved Python 3.0.1 494 Thursday, November 9, 2017 Approved Python
2.7.11 42431 Saturday, December 5, 2015 Approved Python 2.7.10 92013 Saturday,
October 10, 2015 Approved Python 2.7.6 26005 Monday, November 11, 2013 Approved
Python 2.7.5 6548 Monday, May 20, 2013 Approved Python 2.7.4 1980 Sunday, April
7, 2013 Approved Python 2.7.3 6378 Saturday, April 14, 2012 Approved Python
2.7.2.1 929 Friday, February 3, 2012 Approved Python 2.7.2 9860 Tuesday,
September 27, 2011 Approved
Show Additional Versions
Copyright
--------------------------------------------------------------------------------
Copyright © 2001-2024 Python Software Foundation. All rights reserved. Copyright
© 2000 BeOpen.com. All rights reserved. Copyright © 1995-2000 Corporation for
National Research Initiatives. All rights reserved. Copyright © 1991-1995
Stichting Mathematisch Centrum. All rights reserved.
Dependencies
--------------------------------------------------------------------------------
* * python3 (= 3.13.0-rc1)
Discussion for the Python Package
--------------------------------------------------------------------------------
GROUND RULES:
* This discussion is only about Python and the Python 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 Python, 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.
Please enable JavaScript to view the comments powered by Disqus.
SIGNUP FOR THE NEWSLETTER!
Subscribe
Be the first to know about upcoming features, security releases, and news about
Chocolatey.
OVERVIEW
* Getting Started Guide
* Security
* Privacy Policy
* Partner
* Terms of Use
PRODUCT
* C4B Trial
* Pricing
* Support
* Community Packages
LEARN
* Docs
* Courses
* Sitemap
* Blog
CONNECT
* Contact Us
* Support
* Newsletter
* Shop
* Report a Bug
* Status
* *
*
*
*
*
*
*
*
*
* Bluesky butterfly logo
*
© 2024 Chocolatey Software, Inc.
Deployed from 5e3d8fd8c7. You are on EC2AMAZ-AUPJUUI. Page generated 02 Aug 2024
09:19:47 +00:00.
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept