Re: Spyder & Control Panel not working

[Felix Zumstein]

You could try to start spyder from the scripts folder by double-clicking the spyder.bat file. If this also crashes, then try to edit the file like so: 

put a PAUSE at the end, this should keep the command window open so you can read the error message. Not sure if you have to delete/comment out the first line. It should then look something like this:

REM @echo off

call %~dp0env.bat

cd %WINPYDIR%\Scripts

%WINPYDIR%\python.exe spyder %*

PAUSE

double-click the spyder.bat file to start spyder. Did you move the WinPython folder after unpacking? I've had problems with Spyder after doing that.

On Saturday, November 17, 2012 6:04:51 AM UTC+1, Monte Milanuk wrote:

So... downloaded and 'installed' WinPython this evening.  For some reason, I can't get Spyder or the Control Panel to run.  What looks like a DOS box comes up for a few seconds, then some text flashes by too fast to read, and the window closes.  Thats it.

TortoiseHG, PythonInterpreter, IPython all start up normally.

Any suggestions?

[Monte Milanuk]

Downloaded and installed (again) a fresh copy of the 32-bit version to my USB thumb drive.  The machine @ work is a Dell Optiplex 780, running Win XP Pro.  I do not have admin rights.

On Thursday, November 22, 2012 1:31:51 PM UTC-8, Felix Zumstein wrote:

put a PAUSE at the end, this should keep the command window open so you can read the error message.

 
Looks like a permissions problem on spyder.ini?  Seems kind of odd for a fresh install?

Traceback (most recent call last):
  File "spyder", line 2, in <module>
    from spyderlib import spyder
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\spyd
er.py", line 81, in <module>
    from spyderlib.utils.environ import WinUserEnvDialog
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\util
s\environ.py", line 17, in <module>
    from spyderlib.widgets.dicteditor import DictEditor
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\widg
ets\dicteditor.py", line 31, in <module>
    from spyderlib.config import get_icon, get_font
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\conf
ig.py", line 511, in <module>
    set_default_color_scheme(_name, replace=False)
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\conf
ig.py", line 508, in set_default_color_scheme
    set_color_scheme(name, COLORS[name], replace=replace)
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\conf
ig.py", line 499, in set_color_scheme
    value = CONF.get(section, option, default=None)
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\user
config.py", line 257, in get
    self.set(section, option, default)
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\user
config.py", line 323, in set
    self.__save()
  File "E:\WinPython-32bit-2.7.3.1\python-2.7.3\lib\site-packages\spyderlib\user
config.py", line 167, in __save
    conf_file = file(fname, 'w')
IOError: [Errno 13] Permission denied: u'E:\\WinPython-32bit-2.7.3.1\\scripts\\.
.\\python-2.7.3\\..\\settings\\.spyder2\\.spyder.ini'
Press any key to continue . . .

Did you move the WinPython folder after unpacking? I've had problems with Spyder after doing that.

Nope, just put it on the USB drive as part of the install process, then never moved it since.  Isn't part of the whole point of this version supposed to be that it can be moved/copied about *without* problems?

Thanks,

Monte

[Monte Milanuk]

On Friday, November 23, 2012 10:37:12 AM UTC-8, Monte Milanuk wrote:

On Thursday, November 22, 2012 1:31:51 PM UTC-8, Felix Zumstein wrote:

put a PAUSE at the end, this should keep the command window open so you can read the error message.

 
Looks like a permissions problem on spyder.ini?  Seems kind of odd for a fresh install?

...so I looked in that folder, and there was not '.spyder.ini', just '.spyder.ini.bak'.  So I tried copying that to '.spyder.ini'... which WinXP wouldn't let me do from Explorer.  I opened up a console window, and made a copy there... good. Then I ran spyder.bat again... got the same error message?

I opened up the folder in Windows Explorer again, and there was no '.spyder.ini', even though I had copied it and confirmed with 'dir' in the dos/console window earlier.

I opened a console window again, copied '.spyder.ini.bak' to '.spyder.ini' again, checked with 'dir' that it was there, confirmed in Windows Explorer that I could see it there too, and ran spyder.bat once more.  It opened a console window, then a python interpreter... and just before it choked and died and spit out the same trace back message again, I saw the file '.spyder.ini' disappear from Windows Explorer as if it had been deleted...?

Not sure what the heck is going on here; hope this feedback helps track down the problem(s)...

Monte

[JohnP]

I had the same problem on one of my Windows XP Professional labtops
(32bit version of winpython), but not the other. The machine that had
problems had service pack 2, The machine that worked fine had service
pack 3.

[Thomas Haslwanter]

Just downloaded WinPython 2.7.3.3., on a 64bin Win7 machine, and found the following:

i) I have exactly the same problems with Spyder and the WinPython Control Panel not starting - when I install it on a USB.
ii) But when I install it on the C:\ drive, everything works just fine.

The DOS-box comes up too briefly to see what it says.

[Sol Simpson]

I also tried upgrading to 2.7.3.3 about a month ago, from the 2.7.3.1 version I have been using since last summer. I had several issues when using 2.7.3.3; it 'seemed' like it was whenever  I would move the distribution from one computer to another; very strange scipy internal errors and the shell seemed to only be reading the user level environment variables, not the system level ones, so the temporary environment changes being made by the bat were not being picked up fully from what I could tell. 

I just switched back to using 2.7.1 and have 0 issues with it.

>> . But, if this is to run on a locked down lab computer, WINPYDIR could not be set. 

If that is the case then I do not think WinPython will work for you. It needs to set those environment variables for it to work. The important thing to note is that they are only temporary, updated for that console session. When App X ends, the environment settings are unchanged on the PC. This may make no diff to your sys admins though. ;(

>>  what is dp0env.bat? 

%dp0 is a windows batch file 'variable' that is set to the absolute path of whatever directory the currently running batch file is in when it starts, so it allows you to dynamically get what the absolute path of a subdir in WinPython effectively in this case.  The env.bat part is just the name of the batch file that sets the environment up as WinPython needs to for the duration of the app being called.  , so when they are put together you get the absolute path to the env.bat file on your system.

It would be nice if someone could figure out what is causing so many apparent issues for 2.7.3.3; but 2.7.3.1 works just great for my needs in the meantime.

Cheers,

Sol

On Sun, Apr 28, 2013 at 5:35 PM, david jensen <davidje...@gmail.com> wrote:

spyder and control panel do not work, but others I tried did.  Ipython comes up, but no prompt. spyder.bat did not work. Using 2.7.3.3 on xp pro, service pack 3. Tried restarting. Running winpython on same usb drive. Do not understand:

REM @echo off

call %~dp0env.bat

cd %WINPYDIR%\Scripts

%WINPYDIR%\python.exe spyder %*

PAUSE

This was install from my own computer. But, if this is to run on a locked down lab computer, WINPYDIR could not be set. What, also is dp0env.bat?

This is a great idea, I hope this issue can be resolved.

On Saturday, November 17, 2012 12:04:51 AM UTC-5, Monte Milanuk wrote:

So... downloaded and 'installed' WinPython this evening.  For some reason, I can't get Spyder or the Control Panel to run.  What looks like a DOS box comes up for a few seconds, then some text flashes by too fast to read, and the window closes.  Thats it.

TortoiseHG, PythonInterpreter, IPython all start up normally.

Any suggestions?

--
You received this message because you are subscribed to the Google Groups "WinPython" group.

To unsubscribe from this group and stop receiving emails from it, send an email to winpython+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.