Win10 64 bit, Dell XPS13.
A couple of months ago I wrote and continued to run a simple Python program under IDLE 3.7. On 2nd October, this worked fine. On the night of the 2nd, Win10 update to version 1909 ran. (There is a message that the latest update 2004 failed to install in August.) Since then the first line, #!/usr/bin/env python3, gives an invalid syntax error. Microscoft chat help suggested I reinstall Python. So I unistalled 3.7 and tried to install 3.8 from the Python website. This suggested I install the 32 bit, but I found the 64 bit version so downloaded and installed that. Still the same error. Uninstalled that, then installed the recommended 32 bit version.
When I click on my program with a .py extension, the program does not run. If I load IDLE, load the program and run it, I get the invalid syntax error. If I go to "Open with" and choose IDLE from the program folder, I get an error - this app will not run on this computer.
I guess that the Win10 update version 1909 has done something serious to the system, since it isn't reporting correctly to the Python website, nor is it able to run Python/IDLE. So far, no other program appears to be failing, but it is early days yet.
Any ideas welcome.
Thank you
Related
Currently on windows 10, using VSCode to run python.
So I recently downloaded python3.8 when I was using python 3.7. Everything was working fine when I was still on python3.7. I now have multiple python directories and I think my imported libraries are throwing errors because of it.
I now have python in(these are results from searching python and right clicking -> open file location) :
C:\Python38
C:\Users\david\AppData\Roaming\Python\Python38
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Python 3.8
C:\Users\david\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Python 3.7
As for installed programs I have :
python3.8.5(64-bit)
Python launcher
Should I add all four paths to my environment...?
Frankly I don't even know anymore how to tackle this problem. I'm not even sure what the problem is I just think its a problem. If someone could link me another stackoverflow or help that would be great.
If this isn't supposed to be a problem then I guess I have some more googling to do...
Thank you
EDIT(commented below): One specific error I keep on getting is when I install keras and tensorflow, and run a program, it keeps on asking me to install tensorflow 2.2.0 even though I've already installed it. I have C:\Python38 and C:\Users\david\AppData\Roaming\Python\Python38 in my windows path and C:\Python38 as my VSCode path –
So, I have installed python 2.7 along with winpexpect 1.6 (the fork from here: https://bitbucket.org/weyou/winpexpect/wiki/Home). On Win7 everything worked smooth and perfectly. Now I upgraded to Win10 and suddenly the winspawn command hangs up. For example the following command:
import winpexpect
child = winpexpect.winspawn('c:\windows\system32\cmd.exe')
just never comes back. No error message, no exception, no reaction at all.
Does anybody have an idea, what might have happened or what I could do to further investigate the problem?
Add: I run Win10 64 bit, use python 2.7 (Anaconda) 32 bit. When I run a frozen binary (built on the previous Win7 system) along with a stub - everything still works fine. But I can't rebuild it anymore.
Months ago, I installed Python 2.7 on my MacBook Pro (OS 10.8.5) and was using IDLE to run programs for classes I was taking on Udacity. One morning IDLE would no longer start, it would just bounce around on the dock and then close. I was eventually able to get things working again by installing Python 3.3 and using that IDLE.
A few days ago, I tried to get 2.7 working again by uninstalling all versions of Python and reinstalling using Macports. (To uninstall, I simply deleted the Python folders in my application folder, the Python.framework file in /Library/Frameworks and some symlinks in /usr/local/bin. Got the idea from another post here: How to uninstall Python 2.7 on a Mac OS X 10.6.4?)
Now no version of Python is working for me. When I try to start IDLE, I get the following error message in the Console:
2/7/14 10:28:02.556 PM com.apple.launchd.peruser.502[151]: ([0x0-0xc80c8].org.python.IDLE[819]) Exited with code: 1
The Python in the terminal still works, by the way. I also tried installing another IDE, PyCharm, but that doesn't work either (I get a message saying No Python interpreter selected)
If you are using a MacPorts Python, you will need to install the corresponding py*-tkinter port to use any Tkinter-based Python app, including IDLE. Try:
sudo port install py27-tkinter
I'm hearing the call to move my Python code from 2 to 3, so I'm trying to setup Python 3 on my Windows 7 box that already has Python 2.7.5 on it. The python 2 version is 64 bit and so is the Python 3 version that I've most recently installed. I am worried, however, that I might've installed and uninstalled a 32 bit version of Python 3.3.2 by accident and that remnants from it are causing the following error to be thrown when I attempt to edit my code with IDLE.
"The application was unable to start correctly (0xc000007b)."
I checked my registry key and this occurs when the Python 33 Idle is being used. Additionally I tried to use Dependency Walker on it, a program I am unfamiliar with, and got the following "errors." The system cannot find the following files.
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
IESHIMS.DLL
Additionally, I see that Python33.dll is x86 instead of x64.
Copying the answer from the comments in order to remove this question from the "Unanswered" filter:
OK, so I figured out the answer to my own problem and just decided to
answer it here for anyone else who ran, has run, or will run into the
same problem. So the issue is with the Python33.dll. It seems if you
install the 32bit version of Python 3 then install the 64bit version,
you'll still have the 32bit version of the Python 33.dll. I just
deleted the .dll and repaired my 64bit installation of Python 3 and
now the IDLE editor works correctly from the context menu. Who knows
what other errors I have, however :)
~ answer per Karsten Chu
I am trying to get NumPy to work on my new Windows 8 installation, with Python 3.3 installed. When I try (both) installers from here, they crash when I click 'Install'.
Has anyone had success with the same setup?
EDIT: Error image:
It seems, from the capture, that your trying to instal version:
numpy-unoptimized-1.6.2.win32-py3.3.exe
However, I just checked the site this morning, and the latest available version is:
numpy-unoptimized-1.6.2.win32-py3.2.exe
Have you tried the installer again lately (using the latest build)?