Running python files by double click but there is IDLE mismatch - python

I have Python 3.7.4 installed on Windows 10. For some reasons, my "Edit with Python" option doesn't show up when I right click a Python script. So I made "idle.bat" as the default app to run Python scripts from the installed location "C:\Users\ns200\AppData\Local\Programs\Python\Python37". Now when I double click the Python Script, it runs and IDLE 3.7.1 (see picture) shows up with my code. Now when I execute the code, I get "ModuleNotFoundError" though I have all the modules installed(installed using pip3 function for IDLE 3.7.4)
If I open IDLE manually, Python 3.7.4 shell runs and I need to open the script by going to file, open ,choose the file location and IDLE 3.7.4 shows up (see picture). When I execute the script this time, it runs with no errors (as all modules are already installed for 3.7.4).
I don't know why there is an IDLE mismatch here. How can I run IDLE 3.7.4 every time after double clicking the python script with no module error?

you have selected the idle.bat inside py 3.7.1 , Select the idle.bat which is inside python 3.7.4 , your problem will be solved.
python37.4/lib/sitepackages/idlelib/Idle.bat
Approximate path above

Related

running Python 3.9.12 on Pycharm

I have Python 3.9.12 installed on my linux machine at the moment, and it is working fine when I launch a terminal and run a python file. However when I try to do the same in Pycharm, the code does not work properly because the Interpreter is still 3.9.9. Any ideas how I can upgrade the interpreter? I tried to install Conda which has version 3.10, however I cannot seem to be able to attach this interpreter to run my code.
Any help is very much appreciated!
Thank you!
In order to navigate to your options quickly, use CTRL+SHIFT+A, which yields a search bar. When typing in python interpreter it will navigate you to the interpreter settings of PyCharm. When clicking on the settings cog of the defined interpreter, you can select Add.... Select that and you can configure your new interpreter. Please note that you must know where the executable is of the interpreter. If you are unsure, you can use:
import sys
print(sys.executable)

Python IDLE is not launching

Error screenshot of 'python3 -m idlelib'[] [This is where the idle is located]Sample screen shot of the program here I recently deletd my old python program and intsalled a new one but now the Python IDLE is not launching when I click it from the start program. Also tried ruuning as a administartor. But when I open the cmd and type: "python3" I am getting the terminal. But I need to code in the python IDLE.
I have adde the image of the python IDLE, if i click that program the notepad/termiunal is not opening.
I got it solved. It seems my 1. I haven't added my path in the user variablse and 2. In system variables the path given is wrong. And yes as said by #TerryJanReedy I have installed both microsoft and python.org versions, so I deleted all files and carefully re-installed again.

How do I access updated Python 3.9 in VS Code via command line?

I just downloaded VS Code this week and have run into a problem accessing different versions of Python.
When I run a python file called set.py from the command line via python set.py, VS Code is accessing the Python 2.7 version that came with my MacBook. When I run python --version it confirms that VS Code is using Python 2.7.16.
However, when I right-click in the editor and select Run Python File In Terminal it appears to be using the updated version 3.9.4. I have tested this by using an fstring (available in 3.9 but not in 2.7). The fstring code throws an error in the first method but clears fine in the second. Here's my code:
s = set()
s.add(1)
s.add(2)
s.add(3)
print(f"The set has {len(s)} elements.")
And here's my terminal with the results of both methods shown.
Does anyone know what exactly is going on, and how I can execute python files via the command line?
TIA
Specs:
I am running VS Code 1.55.2 and have downloaded Python 3.9.4 to my MacBook Pro running Big Sur 11.2.3
I have also downloaded the Python extension in VS Code and have selected Python 3.9.4 64-bit as my interpreter.
On macOS and linux, you will have a system python that tends to be old and you don't want to touch it because there are system utilities that rely on it.
You will also have the user-installed python, which here is python 3.9.
If the system python is python2, then the command python will typically invoke python2 and the command python3 will invoke python3.
In VS Code on Windows, when you launch a terminal window from the IDE, it will activate the interpreter/environment you've chosen for your project (typically by CTRL-SHIFT-P and then Python: Select Interpreter). I've noticed on Linux that it will not do this (and this may also be the case on macOS), so if I want to use a specific version or environment, I need to specify it or activate it as my first command in the terminal with something like conda activate myenvname.
Unlike in the terminal, VS Code will use the selected interpreter if you run code directly from the IDE (using Run Without Debugging or Control + F5).

Visual Code on Windows can't find module after installing it with PIP. Using wrong Python in Terminal window?

I am using Visual Code 1.47.0 on Windows 8.1 with the latest version of the Python extension installed too. I just installed a module using pip. I then created a new Python file to test it. The IDE highlights the import statement as an error and the drop-down info box says "Unable to import 'extpylib'. If I try to run/debug the test file, I get a traceback error saying:
C:\Users\User\AppData\Roaming\Python\Python38\Scripts
Exception has occurred: ModuleNotFoundError
No module named 'extpylib'
File "C:\Users\user\Documents\PythonProjects\test-extpylib.py", line 2, in <module>
import extpylib
If I run the pip install command again, even with the "--upgrade" command line argument, it says everything is installed and that I'm using the latest build. I am wondering if this is happening because the VSCODE Terminal window is still using Python 2.7, and not the version I have selected in the status bar, which is Python 3.8.3 64-bit? I am not using the Code Runner extension.
I assumeg that this mismatch of versions between the IDE and the VSCODE Terminal window is causing my issue? If so, how can I get the VSCODE Terminal window to use the same version as that which is selected in the IDE? If not, what is the real problem and how can I fix it?
You may have many python paths and VS code is using the wrong one. Choose the right interpreter path just clicking here:
I solved this by closing and re-opening the vs-code after installing new package.
It seems like an environment issue. In my own Visual Studio code integrated terminal, when I type which python and which pip, I get the correct path to both python and pip executables. So this:
I am wondering if this is happening because the VSCODE Terminal window is still using Python 2.7, and not the version I have selected in the status bar, which is Python 3.8.3 64-bit?
Definitely seems to be the issue.
If your VSCODE terminal still uses Python 2.7, you could follow the tips presented here:
However, launching VS Code from a shell in which a certain Python environment is activated does not automatically activate that environment in the default Integrated Terminal. Use the Terminal: Create New Integrated Terminal command after VS Code is running.
and
Note: conda environments cannot be automatically activated in the integrated terminal if PowerShell is set as the integrated shell. See Integrated terminal - Configuration for how to change the shell.
and
Changing interpreters with the Python: Select Interpreter command doesn't affect terminal panels that are already open.
Of course, the package you installed in an environment is independent of other environments.
As you said the VSCode Terminal using Python2.7 while the status bar shows the selected interpreter is Python3.8.3 64-bit. This meaning you are using the global python(3.8.3) to run the python file while you install the package to the Python(2.7) environment.
Solution:
After you selected the python interpreter in the status bar, you need to activate the environment in Terminal through shortcut 'Ctrl+Shift+`'. You can through these commands to check which environment you are using:
In the terminal:
By command "pip --version" to check which pip you are using.
By command "python" -> "import sys; sys.executable" to check which python you are using.
By command "python" -> "import sys; sys.path" to check which 'site-package' the interpreter searching for.
pip command that was used to install the package is based on a different version of python versus what VS Code is using.
Check the python version of your pip command, run pip --version. For example, on my system, this is the output of this command.
$ pip --version
pip 22.0.4 from /Library/Python/3.8/site-packages/pip (python 3.8)
Check the version of code that VS code is using. For VS code 1.61, the python version will be visible at the bottom left corner while a python file is open in the editor. Screen shot of the same is given below. You can also observe from the screen shot that lazy_streams package is not being recognised by VS code.
To solve the error in VS code, update the python version in VScode to be same as that of pip. Updating of the version can be done by simply clicking on the Python version displayed, which will further prompt you to select among all available python versions on your system.

Python no longer launches from command prompt after windows update

My Windows 10 computer just installed updates and now when I go to the command prompt and type "python" the Windows store opens with a download option.
My path already includes two versions of Python for some reason:
C:\Users\Josh\AppData\roaming\Python\Python37\
C:\Users\Josh\AppData\Local\Programs\Python\Python37
Any suggestions? I can type in a python script (think.py) and it runs as expected, but python think.py does nothing.
python should work in cmd if Python is correctly installed and added to Windows path. py also exists and allows for a specification of a version i.e. py -2 or py -3. In your case it appears that python is installed in appdata and not program files, and this is most likely the issue with the python command not working! Here is a pretty comprehensive article on the differences between the two!

Categories