On 01/16/2013 01:38 AM, David Verelst wrote:
Hi,
I am not a developer here, but I don't think that is intended behaviour.
On other platforms, such as mine, it works as expected (no need to wrap
it in show()). As Monte mentioned, maybe this is an issue related to the
Debian/Ubuntu package? I don't know if it will help, but you could try
to run spyder from source
Yeah... I've been kicking this idea around, but not sure I want to
commit just yet - mainly because I'm normally a fan of using the package
manager on systems like this as much as possible. Kind of a six one
way, half-dozen the other dilemmas as far as which one is more
frustration - dealing with out-of-date semi-broken version supported by
the system package manager, or compiling from source and having to hunt
down dependencies manually and pin packages at specific versions to
support the same. I haven't tried it for spyder, so it may be a lot
less painful than that... but BTDT in the past.
FWIW... I wonder if part of the problem ties back to the fact that
spyder (2.1.10 in this case) has problems with recognizing the ipython
installation. If I set the option in the preferences to start an
ipython kernel at startup I get all sorts of errors/warnings in the
internal console log... and several of the ipython option check boxes
are greyed out, including starting an ipython interpreter console at
startup - citing the reason as that it (spyder) can't find a version of
ipython >= 0.10 installed on the computer in question. Odd, since it'll
let me manually open an ipython interpreter from the console window
menu, and ipython is clearly @ 0.13 release version on this machine.
--
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.
