On Feb 22, 4:50 am, Pierre Raybaut <[email protected]> wrote:
> But, you are perfectly right, this could be very helpfull to
> beginners. This kind of 'new comer' point of view is most welcome
> here: it helps the software to fit everyone needs.
>
> I'll see what I can do:http://code.google.com/p/spyderlib/issues/detail?id=563
I appreciate that; it's my only current complaint with Spyder.
FYI - About 6 weeks ago I decided to learn Python and try to
transition to it (from MATLAB). I researched online and decided
Spyder [actually Python(x,y)] sounded the best.
Then I ran into the problems I described in my other posting
("Strangeness"), and decided that Spyder was just too immature and
buggy for regular use.
So I tried a bunch of other things:
Pydev/Eclipse (couldn't get it working),
Python/NetBeans (works great until you try to debug - then it
crashes constantly),
Python/IDLE (debugger didn't work at all for me)
iPython+pyreadline+vim+Console2 (horrible un-integrated debugging)
So I came back and tried Spyder again (which I liked the best in the
first place, if only it would work) - to my surprise Spyder _without_
Python(x,y) works fine!! (So far, anyway.)
So THANK YOU for Spyder - it is exactly what I was looking for, and
other than the small matter of tab stops, does exactly what I want.
Some small suggestions for improvement:
* I found that I had to install Python27, QT, pyReadLine, iPython, and
Spyder 2.0.6 IN THAT EXACT ORDER to make iPython work in Spyder. That
should be documented, I think.
* It would be really nice to know what all the many controls and
options in Spyder do - documentation seems lacking.
Cheers,
--Dave
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
