Releases: DavidWhittingham/ps-EnablePython
Releases · DavidWhittingham/ps-EnablePython
ps-EnablePython v2.3.3
Fixes
- Fixes issue with quote interpretation on PowerShell 7 vs older versions
ps-EnablePython v2.3.1
Fixes
- Fixed a series of bugs that could cause error message when trying to run
get-python
ps-EnablePython v2.3.0
New Features
- Conda is now activated automatically when enabling a Python install that is part of a Conda environment (works with versions of Conda that support PowerShell activation)
- Get-Python now detects the "all users" install of Python that comes with ArcGIS Pro. Note that even though this version of Python is part of a Conda environment, the version of Conda that ships with ArcGIS Pro is too old for the environment to be activated
EnablePython v2.2.0
New Features
- User installed site-packages in Python are effectively broken on Windows when working with multiple different platforms, i.e. 32-bit and 64-bit Python, as Python uses the same directory and this breaks any packages that are platform specific. As such, EnablePython now overrides the user base by default to make it platform-specific path. In the event that you don't want to override this, there's now a
-NoPlatformUserBaseswitch.
Fixes
- The scripts directory for user-installed site-packages is now added to PATH
EnablePython v2.1.0
EnablePython v2.0.2
Fixes
- (#1) Fixed an issue getting Python version information when PYTHONHOME was set
EnablePython v2.0.1
Fixes
- Fixed an issue running on PowerShell Core
EnablePython v2.0.0
New Features
- Expanded support to any Python install that registers itself according to PEP 514 conventions
EnablePython v1.0.0
Changes
- Made the
$Versionparameter optional, now picks the highest available version (respecting$Platformparameter if supplied)
EnablePython v0.1.1
Fixes
- Uninstalled Python versions are no longer listed with
Get-Python