Bug reports: Spyder 2.1.6 on Windows x64

[NerdFever.com]

I've been following the progress of Spyder on the list for months; I'm
excited to finally ready to jump in and give it a try.

On a Windows 7 x64 machine, I installed Python 2.7.2 (x64 version)
into c:\Program Files\python272, then installed Spyder 2.1.6 using the
Windows installer.

1 - Spyder won't run that way. It flashes up a command window and
then erases it too fast to read.

2 - Poking around in Scripts, I see that "spyder.bat" references "c:/
python27", which is not where Python is actually installed. So maybe
this is part of the reason why it doesn't work. I think Spyder ought
to use the actual Python install location (as recorded in the
registry, I think).

3 - I then uninstalled Spyder (and then Python) in order to try
again. After Spyder un-installs (successfully, I think), it doesn't
remove the "Python 2.7 - spyder 2.1.6" entry from the Programs and
Features list in Windows. This has to be removed manually.

Not really a bug, but a comment:

4 - As a brand-new user, I find it confusing whether I should download
and install the "standalone" (spyder-win32-sa-2.1.6.zip) or the
"installer" (spyder-2.1.6_py27.exe). The online documentation doesn't
mention either one.

Some guidance on which file(s) to install, in what order (including
any dependencies), would be helpful for newbies.

[matt]

I am not an expert, but I do have spyder working on a Windows 7 machine

 with 64 bit python so I will try to help you

> On a Windows 7 x64 machine, I installed Python 2.7.2 (x64 version)

> into c:\Program Files\python272, then installed Spyder 2.1.6 using the

> Windows installer.

First, I would ask by what method you installed it.  It is not as simple

to get it running on 64 bit windows because there isn't a good package

like python x,y or enthought.  I would point you to this list of compiled

binaries

http://www.lfd.uci.edu/~gohlke/pythonlibs/

 

> 1 - Spyder won't run that way.  It flashes up a command window and

> then erases it too fast to read.

What happens if you navigate to your site-packages(in your case probably

c:\Program Files\python272\Libs\site-packages) folder and run

python spyder.py 

at the command prompt?

> 2 - Poking around in Scripts, I see that "spyder.bat" references "c:/

> python27", which is not where Python is actually installed.  So maybe

> this is part of the reason why it doesn't work.  I think Spyder ought

> to use the actual Python install location (as recorded in the

> registry, I think).

Honestly, I am not sure if this is a problem or not, but sometimes *nix

based systems don't play well with spaces in path names.  That is why

typically the install goes to c:\python27.  It would make your life

easier if you installed python there, but I'm not sure if it matters in

this case.

> 3 - I then uninstalled Spyder (and then Python) in order to try

> again.  After Spyder un-installs (successfully, I think), it doesn't

> remove the "Python 2.7 - spyder 2.1.6" entry from the Programs and

> Features list in Windows.  This has to be removed manually.

> 

> Not really a bug, but a comment:

> 

> 4 - As a brand-new user, I find it confusing whether I should download

> and install the "standalone" (spyder-win32-sa-2.1.6.zip) or the

> "installer" (spyder-2.1.6_py27.exe).  The online documentation doesn't

> mention either one.

> 

> Some guidance on which file(s) to install, in what order (including

> any dependencies), would be helpful for newbies.

Some notes on install can be found here:

http://code.google.com/p/spyderlib/wiki/Installation

You probably have to try the hard way if you want 64 bit, although I am

sure python x,y is working on a 64 bit version and it may already work.

You might want to check their website.

[matt]

I am not an expert, but I do have spyder working on a Windows 7
machine
with 64 bit python so I will try to help you

> On a Windows 7 x64 machine, I installed Python 2.7.2 (x64 version)
> into c:\Program Files\python272, then installed Spyder 2.1.6 using the
> Windows installer.

First, I would ask by what method you installed it. It is not as
simple
to get it running on 64 bit windows because there isn't a good package
like python x,y or enthought. I would point you to this list of
compiled
binaries
http://www.lfd.uci.edu/~gohlke/pythonlibs/

> 1 - Spyder won't run that way.  It flashes up a command window and
> then erases it too fast to read.

What happens if you navigate to your site-packages(in your case
probably
c:\Program Files\python272\Libs\site-packages) folder and run
python spyder.py
at the command prompt?

> 2 - Poking around in Scripts, I see that "spyder.bat" references "c:/
> python27", which is not where Python is actually installed.  So maybe
> this is part of the reason why it doesn't work.  I think Spyder ought
> to use the actual Python install location (as recorded in the
> registry, I think).

Honestly, I am not sure if this is a problem or not, but sometimes
*nix
based systems don't play well with spaces in path names. That is why
typically the install goes to c:\python27. It would make your life
easier if you installed python there, but I'm not sure if it matters
in
this case.

> 3 - I then uninstalled Spyder (and then Python) in order to try
> again.  After Spyder un-installs (successfully, I think), it doesn't
> remove the "Python 2.7 - spyder 2.1.6" entry from the Programs and
> Features list in Windows.  This has to be removed manually.
>
> Not really a bug, but a comment:
>
> 4 - As a brand-new user, I find it confusing whether I should download
> and install the "standalone" (spyder-win32-sa-2.1.6.zip) or the
> "installer" (spyder-2.1.6_py27.exe).  The online documentation doesn't
> mention either one.
>
> Some guidance on which file(s) to install, in what order (including
> any dependencies), would be helpful for newbies.