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.
Related
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
I'm trying to install several plug-ins in Spyder IDE, such as:
unit test
notebook
line profiler
spyder-terminal
memory-profiler
spyder-report
But unfortunately, I've got some serious problem. The installation was good, though I couldn't install spyder-vim and conda-manager plug-in for some unknown reason.
But the thing was horrible after launching the IDE. It's just broken somehow and not responding. Mouse unclickable. The interface was totally messed up.
After removal of these plug-ins, I again manually installed those plug-ins and tried to figure it out which plug-in caused this.
This time I only installed
unit test spyder-report notebook terminal
and now after launching, I saw interface was a little bit finer than before and discovered some problem in the spyder-report plug-in. While rendering report to HTML it showed the following error:
signal only works in main thread
I'm not sure whether I'll try other plug-in, but everything is pretty OK now except the spyder-report plug-in. I googled it for a day, but I found no effective solution.
You didn't say which version of Spyder and Python you installed, nor which operating system you are using. So, using Debian unstable and Python 3.6.5, I installed:
spyder3, 3.2.6
spyder-common, 3.2.6
python3-spyder, 3.2.6
python3-spyder-memory-profiler, 0.1.2
python3-spyder-line-profiler, 0.1.1
python3-spyder-reports, 0.1.1
python3-spyder-unittest, 0.3.0
as well as all of their dependencies. After that, I started spyder3 without any problems (except that I have to use the Spyder 2 icon theme, because it can't find the Spyder 3 icons). The Reports tab works fine, no "Signal only..." error.
The problem with spyder-vim seems to be that no actual release has been made yet, so pip3 install spyder-vim doesn't find anything.
Last, I added the terminal plugin with pip3 install spyder-terminal.
Again, after that all is working fine.
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
So I didn't look carefully and I installed 64 bit Python2.7 on an OS X 10.5 box. This didn't work with the standard cryptic wrong-OS message "dyld: unknown required load command"
OK, fair enough
So I dragged the Python2.7 icon to the trash from Applications; then I went in with sudo and renamed the
/Library/Frameworks/Python.framework/Versions/2.7/
to
/Library/Frameworks/Python.framework/Versions/2.7BROKEN/
and installed the 32-bit Python 2.7. But I am still getting the "dyld" error. Any idea what other side effect the broken install might have had to make this possible and how I can fix it?
Problem solved by following this bug report's instructions, substituting 2.7 for 2.6 everywhere, then reinstalling.