Yes, Spyder doesn't start correctly under our version of SLES 11, but this
is not a straightforward installation, so it probably is not indicative of
a general problem on SLES 11. We have built many packages from source,
including Qt and PyQt, so the problem is most likely with our build, I just
wasn't sure how to track it down. Thanks for the information in
.spyder.ini, I should now be able to install and set it up for users.
Robert
On Thursday, September 6, 2012 12:10:55 AM UTC+10, Carlos Córdoba wrote:
>
> Hi Robert,
>
> CONF reads the file ~/.spyder2/.spyder.ini. Look there for a section
> called [inspector]; the 'enable' option is inside it.
>
> Sorry for not answering your first email, but if I understood it
> correctly, are you saying that Spyder doesn't start correctly under SLES
> 11? That's really strange because Qt and PyQt versions seem to be the
> latest ones.
>
> Cheers,
> Carlos
>
> El 03/09/12 22:19, rdenham escribió:
>
> I've managed to narrow the problem down to a couple of plugins, inspector
> and online help widget. Online help doesn't surprise me, since we are
> behind a proxy and access to online stuff is always problematic. Not sure
> about the problem with the inspector plugin, but we can live without it for
> a while I guess.
>
> I disabled these in a pretty ugly way. In the file spyderlib/spyder.py, on
> line 668, I see:
> if CONF.get('inspector', 'enable'):
>
> I just commented out the self.inspector.register_plugin() line.
> I wasn't sure of the way CONF.get works, I tried setting enable to false
> in config.py, but this didn't seem to work. What file is CONF.get reading
> to determine whether 'inspector' 'enable' is True or False?
>
>
> Robert
>
>
>
> On Monday, August 27, 2012 10:33:53 AM UTC+10, rdenham wrote:
>>
>> Hi, we've been running spyder on our Suse Linux machines, but our system
>> is quite old. We're about to upgrade to SLES11, and I wanted to check that
>> spyder runs. Unfortunately, my testing wasn't very positive. I get up to
>> the splash screen, with the message loading object inspector, where it
>> just hangs. Debugging doesn't tell me much. I tried the bootstrap approach,
>> which doesn't get any further. Here is the output:
>>
>> $ python bootstrap.py
>> Executing Spyder from source checkout
>> abort: repository /opt/sw/fwsrc/rsc/spyder/spyder-2.1.11 not found!
>> Error: Failed to get revision number from Mercurial - need more than 0
>> values to unpack
>> 01. Patched sys.path with /opt/sw/fwsrc/rsc/spyder/spyder-2.1.11
>> 02. No PySide detected, using PyQt4 if available
>> 03. Imported Spyder 2.1.11 (Qt 4.8.2 via PyQt4 (API v2) 4.9)
>> 0x. Enforcing parent console (Windows only)
>> 04. Executing spyder.main()
>> Killed
>>
>> I then have to kill the process.
>>
>> If I use spyder -l, I get the basic interface no problems.
>>
>> Any suggestions about working through this would be appreciated.
>>
>> Thanks
>> Robert
>>
> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/spyderlib/-/TjIbKmZufQ0J.
> To post to this group, send email to [email protected]<javascript:>
> .
> To unsubscribe from this group, send email to
> [email protected] <javascript:>.
> For more options, visit this group at
> http://groups.google.com/group/spyderlib?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/spyderlib/-/agI6bC1YnIAJ.
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.
