Hi Matt,

Thanks for reporting the problem. I don't fully understand what's happening. Here are my questions to you:

1. Does Spyder freezes and you have to manually kill it? Or does it just crash before you can do something on it? If the case is the last one, do you receive a segfault warning on the console or you can see a Python traceback?

2. Does your windows account have non-ascii characters?

3. Could you reset your spyder settings and start afresh to see if that solves the problem? You can do it with:

python bootstrap.py -- --defaults

and if that doesn't work with

python bootstrap.py -- --reset

4. Please also tell us your exact Python and PyQt versions (Note that Spyder doesn't work too well with PySide and it usually segfaults).

Cheers,
Carlos

El 14/05/12 14:46, Matt Anderson escribió:
The first bad revision is:
changeset:   2041:3bed38623049
parent:      2040:1cd7dc4233ce
parent:      2031:c27ddf06569e
user: Carlos Cordoba <[email protected] <mailto:[email protected]>>
date:        Tue May 01 22:25:05 2012 -0500
summary: Merge: Make Spyder start and work on non-ascii user accounts on Win
dows

Not all ancestors of this changeset have been checked.
Use bisect --extend to continue the bisection from
the common ancestor, aaddf3e325fa.

If I extend it, I get

The first bad revision is:
changeset:   2014:b5670c37c544
parent:      2012:aaddf3e325fa
user: Pierre Raybaut <[email protected] <mailto:[email protected]>>
date:        Sun Apr 15 15:15:00 2012 +0200
summary: Added memory and CPU usage status bar widgets (see Preferences/Gene
ral)

But somewhere in there between the two, and including 2014 the gui never loads at all(however, 2030 works). 2041 looks like a pretty big merge so I'm not sure how much that helps.

Matt

On Mon, May 14, 2012 at 12:43 PM, Jed Ludlow <[email protected] <mailto:[email protected]>> wrote:

    On Mon, May 14, 2012 at 10:26 AM, Matt Anderson
    <[email protected] <mailto:[email protected]>> wrote:

        The main gui fully loads, in debug mode it gets to ***end of
        main window setup*** and then gives a couple of warnings about
        already having imported pyflakes/rope and adding site-packages
        to the sys.path.

        It actually crashes somewhere in the app.exec_() call of
        spyder.py(1868).  Around the time it lodes the object
        inspector(sometimes I see the object inspector details before
        it crashes, sometimes not).


    It would be very helpful if you could figure out which specific
    commit caused the problem. You were successfully running from
    source at one point, and now the latest changes are causing you
    problems. Are you familiar with hg bisect?

    http://www.selenic.com/mercurial/hg.1.html#bisect

    It's a bit easier to run from TortoiseHg, but it can be done from
    the command line, too. Would you be willing run a bisect and
    pinpoint the revision where the problem first shows up?
-- You received this message because you are subscribed to the Google
    Groups "spyder" group.
    To post to this group, send email to [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:spyderlib%[email protected]>.
    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 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.

--
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.

Reply via email to