In PowerShell, Get-Command python | fl * will tell you which Python executable it's finding and show you details about where it is.
- You can check Settings -> Apps and Features, or Control Panel -> Programs and Features. They will show you distinct versions of Python you installed, but that might not be enough if Python is installed as part of some other toolkit or program.
- If Python 2.7.11 is there, select it and click uninstall. If it's not there, see if you can tell what it's installed with, from the output of
Get-Commandearlier, and decide if you want to remove that. - How PowerShell chooses what to run when you type a command is explained in help about_Command_Precedence, and is:
- Alias
- Function
- Cmdlet
- Native Windows commands
At the point of "Native Windows commands", it goes to the PATH environment variable, a semi-colon separated list of path names, which get searched in order, looking for a matching executable file.
You can see the folders with:
$Env:PATH -split ';'
And you can watch PowerShell identify what to run for 'python' with the command
Trace-Command –Name CommandDiscovery –Expression {get-command python} -PSHost
So, to make Python 2.7.13 the one to launch, you could:
- make it the only Python version available.
- move its folder to the front of the PATH list, ahead of any other version. See: What are path and other environment variables, and how can I set or use them - question on SuperUser.com
- make a batch file to launch it called python.bat in a folder in the PATH ahead of other versions.
- make an alias (in your PS Profile) named python to launch the one you want (
New-Alias -name python -Value C:\Python27\python.exe, etc).
In PowerShell, Get-Command python | fl * will tell you which Python executable it's finding and show you details about where it is.
- You can check Settings -> Apps and Features, or Control Panel -> Programs and Features. They will show you distinct versions of Python you installed, but that might not be enough if Python is installed as part of some other toolkit or program.
- If Python 2.7.11 is there, select it and click uninstall. If it's not there, see if you can tell what it's installed with, from the output of
Get-Commandearlier, and decide if you want to remove that. - How PowerShell chooses what to run when you type a command is explained in help about_Command_Precedence, and is:
- Alias
- Function
- Cmdlet
- Native Windows commands
At the point of "Native Windows commands", it goes to the PATH environment variable, a semi-colon separated list of path names, which get searched in order, looking for a matching executable file.
You can see the folders with:
$Env:PATH -split ';'
And you can watch PowerShell identify what to run for 'python' with the command
Trace-Command –Name CommandDiscovery –Expression {get-command python} -PSHost
So, to make Python 2.7.13 the one to launch, you could:
- make it the only Python version available.
- move its folder to the front of the PATH list, ahead of any other version. See: What are path and other environment variables, and how can I set or use them - question on SuperUser.com
- make a batch file to launch it called python.bat in a folder in the PATH ahead of other versions.
- make an alias (in your PS Profile) named python to launch the one you want (
New-Alias -name python -Value C:\Python27\python.exe, etc).
This was a question about python 2.7, but probably it will be useful to give an answer for the versions above 3.3 too:
Previously, multiple versions (also environments, also they are specific folders) of python on the same system was rare, and placing the only available python.exe directly in PATH was acceptable. Currently, multiple installed python versions will conflict and override each other if simply placed that way.
After 3.3 a python launcher was introduced which detects and activates one of the installed versions automatically. It is supposed to be placed in PATH instead of any python executable.
So in this modern situation, Get-Command python | fl * may give you nothing or nothing helpful.
And to run scripts or to get available versions, use launcher:
- ensure you have it:
tryGet-Command pycommand from the PowerShell. If launcher is missing, it can be installed with the official installer. There is a separate checkbox for the launcher which is enabled by default. - if install is correct, command
py --list-pathswill give a summary on the installed versions, and supposed way to run scripts is not previouspython main.py, but commands likepy main.pyorpy -3.5 main.py. Runpy --helpfor more info.
Additional confirmation that intended way changed.
Just to give an idea, launcher is not the only way to activate, this also can be done by a simple command.
For example, there is a version under D:\python_install\python.exe. But it's not in the PATH and python command correctly ends with not found error or opens Windows Store. An additional command in cmd or bat SET PATH=D:\python_install\;%PATH% or PowerShell $env:Path = "D:\python_install\;" + $env:Path temporarily activates that specific version, and python will work as previously during that specific run.
Videos
I work in a Microsoft shop so naturally I adopted PowerShell and in almost all cases it just seems to work so flawlessly. Obviously, Python is significantly more adopted. I'm just curious where Python really excels over PowerShell. I would love to learn the language, but like I said I work in a Microsoft shop and I just never can find something that PowerShell can't easily achieve.
I'm a .Net stack developer and know PS very well but I've barely used Python and it seems like Python has been constantly moving towards being the mainstream language for a myriad of things.
I see Microsoft adding it to Excel, more Azure functionality, it's #1 for AI/machine learning, data analysis, more dominate in web apps, and seemingly other cross platform uses.
I've been hesitant to jump into the Python world, but am I wrong for thinking more of my time should be invested learning Python over PowerShell for non-Windows specific uses?
Or how do people familiar with both PS & Python feel about learning the languages and their place in the ecosystem?
If Python feels more natural to you and helps you learn valuable skills, it’s perfectly fine to use it for Windows scripting. While PowerShell is often more concise for OS-related tasks and is natively integrated into Windows, Python offers greater flexibility, cross-platform compatibility, and broader use cases beyond scripting. You may occasionally need PowerShell for deep Windows integration (e.g., registry edits, GPO management), but for general automation, Python is a solid choice, especially if it aligns with your learning goals and future career prospects.
Hi everyone,
I wanted advices on which language to use for scripting purposes on Windows. I know it depends a lot on the script that I want to make but generally speaking, is Python an OK language to script in for basic OS related tasks or should I go with Powershell ?
I actually did write a basic script which allows me to clear my MS Teams cache on startup in both languages and even though Powershell is way shorter I still prefer the way Python does it. A big plus for me is that by writing scripts in Python I am learning more about it and since you can use it for various programming purposes (other than scripting) I will be gaining some really valuable skills by doing so…
I understand Python a lot more easily than Powershell at the moment and I know that Python is not (yet) integrated in Windows by default but it feels way more natural to me so I am thinking about just doing every scripting tasks with it. Since most of the companies out there are using Python in their prod env, is it OK to use it instead of traditionnal Powershell ?
Possibly because after python 3.3 intended command is not python, but simply py
Detailed explanation here
And short answer to your question:
check if powershell command py -0p --list-paths finds any versions.
I am using Windows 11, Python3.10 and Laptop, and Windows Powershell cannot show Python version (command: python --version).
Solution: type Python inside Windows Powershell, it will prompt out Microsoft Store, just click "get", wait to finish the process, then go to Windows Powershell, type "python --version", it can show the Python version.
» pip install pypsrp
Stupid question - but I have a pretty solid grasp on PowerShell - is there like a list out there of Python vs PowerShell equivalents?
So for this is what I have:
Get-Member Equivalent - dir(object)
Get-Member Equivalent - type(object)
Get-Help Equivalent - help(object)
I just started learning Python 3 recently and the course I'm learning it from "Python for Everybody by Dr. Charles Severace". In the lessons, he uses Command Prompt to run his code. I've also heard that Powershell is basically the same thing as CP, just that it can do more. The question is, should I switch over to PS now, or does it not matter when just as long as I get to know how to use both eventually?