Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spyder has several problems to start on Windows because pywin32 is not installed #1441

Closed
spyder-bot opened this issue Feb 17, 2015 · 15 comments

Comments

@spyder-bot
Copy link
Collaborator

From Prof.Tod...@gmail.com on 2013-06-11T09:17:59Z

Please note that reporting bugs from Spyder's help menu ("?" > "Report
issue...") will fill version details for Spyder, Python and Qt in this description for you.

What steps will reproduce the problem?

1.install spyder 2.2.0 for windows
2.run spyder and get msg that it needs qt4
3.download and install qt4
4.run spyder again - it works ok
5.while spyder is running, close the little popup dos box - spyder quits
6.try to run spyder again - dos box appears for half a sec then disappears
7.spyder won't ever run again What version of the product are you using? On what operating system? spyder 2.2.0; qt4 10.1; windows xp pro sp3 fully updated; hardware plateform is dell vostro 1500 laptop, 1gb ram, intel core 2 duo cpu

Please provide any additional information below

. I tried reinstallation of both spyder and qt4 - same results
I removed all python products from my computer and reinstalled - same results

Note: the program worked until i killed the stupid little dos box. clearly something is hiding somewhere (probably registry) that is keeping spyder from ever starting again.

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1441

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-06-29T06:45:29Z

issue #1408 has been merged into this issue.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-06-29T06:45:45Z

issue #1409 has been merged into this issue.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-06-29T08:31:19Z

Sorry for my late response. The problem you are experiencing is most probably due to the fact that you don't have installed a module called "pywin32", so please install it and tell us if you can make Spyder running again.

Summary: Spyder has several problems to start on Windows (was: killing dos box window without doing a normal exit in spyder, keeps spyder from ever running again.)
Labels: -Usability MS-v2.3

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-06-29T08:42:49Z

issue #1453 has been merged into this issue.

@spyder-bot
Copy link
Collaborator Author

From techtonik@gmail.com on 2013-07-01T01:11:23Z

For the file systems without symlinks (FAT32 is Spyder is run from USB), the locking mechanism will in ./utils/external/lockfile.py may fail to auto cleanup the created symlink if process crashes.

If that is the case, we may write process id into the spyder.lock and manually check if that process is still running on Spyder startup.

@spyder-bot
Copy link
Collaborator Author

From techtonik@gmail.com on 2013-07-01T05:59:05Z

I am not sure that the problem with "killing dos box window" should be generalized to "several problems".

@spyder-bot
Copy link
Collaborator Author

From techtonik@gmail.com on 2013-07-01T06:00:08Z

issue #1408 has been merged into this issue.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-07-01T06:30:19Z

I'm almost sure all these problems all related to the lack of pywin32, that's why I decided to put them together.

@-Anatoly: Regarding your concern about FAT32, there are two things worth mentioning:

  1. Pierre and Jed would have noticed several months ago if something was wrong with running Spyder from a USB, because they run WinPython.
  2. Spyder is able to start even if the lock file (or dir, on Windows) was not cleaned up on the last session. That's the beauty of it, we don't to worry about cleaning it up in case of a crash. lockfile.py uses it to read the pid of the process that created it, and if it can't find it then starts a new session.

Summary: Spyder has several problems to start on Windows because pywin32 is not installed (was: Spyder has several problems to start on Windows)

@spyder-bot
Copy link
Collaborator Author

From techtonik@gmail.com on 2013-07-01T07:23:33Z

Ok. In that case a backport fix should be enough. 2.3 contains changes that break PySide stuff with Python 3 support, and it behaves unstable even with PyQt4 on Ubuntu.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-07-01T12:15:21Z

I wouldn't like to backport your changes because of these reasons:

  1. I haven't had time to test them and probably very few people has done it, because we haven't released 2.3beta1. We should let them live a little bit more.

  2. We plan to release 2.3 at the end of the month or at most mid August.

  3. The current solution is working fine, people just needs to install pywin32 (and probably there isn't too much people without it now that Anaconda is shipping it now too).

@spyder-bot
Copy link
Collaborator Author

From ruchirte...@gmail.com on 2013-08-18T02:35:51Z

I had exactly the same issue and finding and deleting the spyder.lock/symlink file fixed it. I installed anaconda 1.6.2 recently and still had this issue. Not sure why pywin32 is relevant here - the project page does not say and I have python working on windows already. Checked that pywin32 does exist on my system under anaconda.

@spyder-bot
Copy link
Collaborator Author

From rajiv...@gmail.com on 2013-09-04T17:24:59Z

I came across this issue recently as well. If I understand this correctly, the "auto cleanup" procedure (ie: searching for the PID written in the lock file) only works if pywin32 is installed. Otherwise start_app.py will not run the program.

What made this really irritating for me is that the start_app.py script just fails silently if it fails to acquire the lock (I had to use the debugger to actually figure out what was going on).

Maybe if the start_app.py script could report an error eg. "Failed to acquire lock" this would make the error much easier to diagnose and fix. I don't have a problem with installing pywin32, it would just be good to have some notification of the error rather than a silent failure.

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-09-04T20:14:22Z

Sorry for the inconvenience. This is already fixed in our development branch by getting rid of pywin32. We hope to release this version in about a month and a half.

Status: Accepted

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2013-11-04T09:50:53Z

There is still some work to do to finish 2.3, but I finally have time to test Anatoly's changes to fix this issue and they are working great! Kudos to him for getting rid of pywin32!

I can say this fixed now.

Status: Verified
Owner: techtonik@gmail.com
Labels: -Priority-Medium Priority-High

@spyder-bot
Copy link
Collaborator Author

From techtonik@gmail.com on 2013-11-06T04:33:22Z

Glad that helped. ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant