[Eric] Re: eric 4.1.1 interactive python console problem

[Detlev Offenbach]

Hi,

can you please check, if the IDE is listening on a port? Can you try to start 
the debugger backend manually via the shell context menu 'Start->Python' 
entry?

Detlev

On Samstag, 12. April 2008, Melissa wrote:
> Detlev Offenbach <detlev at ...> writes:
> > On Mittwoch, 9. April 2008, Melissa wrote:
> > > I am having the same socket error (see traceback below) on my recent
> > > installation of Eric4 on Windows Vista upon launching. In the
> > > configuration panel: Debugger > General (Part 1), I have selected:
> > >
> > > Only selected network interface: 127.0.0.1
> > > Passive Debugger is unchecked
> > > Remote Debugger is unchecked
> > >
> > > Nothing is checked on the General (Part 2) configuration page.
> > >
> > > The problem does not seem to be the firewall since I deactivated the
> > > firewall and launched Eric4 and have the same error message.
> >
> > Please check the settings of your firewall. Maybe it is too prohibitive.
> > Except from this I have no idea. Unfortunately I cannot test on Windows
> > Vista. Maybe somebody else can help out.
> >
> > Regards,
> > Detlev
>
> I turned the firewall off and still have this error. I'm only using the
> loopback anyway, not connecting remotely. I've got MySQL installed as well
> and don't have any trouble opening the database on localhost.
>
> The shell is essentially disabled by this error. I can hit return and it
> goes to a new line, but no prompt and I can't type anything in.
>
> Can anyone give me another clue as to a diagnostic I could do to better
> pinpoint the problem?
>
>
> Another thing I tried is turning passive debugger on and that did not go
> well. I got this unhandled exception when I hit return in the shell window:
>
> ---------------------------------------------------------------------------
>----- 2008-04-12, 00:13:13
> ---------------------------------------------------------------------------
>----- exceptions.AttributeError:
> 'NoneType' object has no attribute 'remoteStatement'
> ---------------------------------------------------------------------------
>----- File
> "C:\apps\Python\Lib\site-packages\eric4\ViewManager\ViewManager.py", line
> 4308, in __editorCommand
>     e4App().getObject("Shell").editorCommand(cmd)
>   File "C:\apps\Python\Lib\site-packages\eric4\QScintilla\Shell.py", line
> 613, in editorCommand
>     self.supportedEditorCommands[cmd](cmd)
>   File "C:\apps\Python\Lib\site-packages\eric4\QScintilla\Shell.py", line
> 761, in __QScintillaNewline
>     self.__executeCommand(buf)
>   File "C:\apps\Python\Lib\site-packages\eric4\QScintilla\Shell.py", line
> 1007, in __executeCommand
>     self.dbs.remoteStatement(cmd)
>   File "C:\apps\Python\Lib\site-packages\eric4\Debugger\DebugServer.py",
> line 690, in remoteStatement
>     self.debuggerInterface.remoteStatement(stmt)
>
> ---------------------------------------------------------------------------
>----- Version Numbers:
>   Python 2.4.5
>   Qt 4.3.3
>   PyQt4 4.3.3
>   sip 4.7.4
>   QScintilla 2.2
>   eric4 4.1.2 (r2105)
>
> Platform: win32
> 2.4.5 (#71, Mar 26 2008, 17:55:58) [MSC v.1310 32 bit (Intel)]
> ---------------------------------------------------------------------------
>-----
>
> I'm using PythonWin with no problem* and I've tested Qt and PyQt with no
> problem so far.
>
> *I'd like to switch to Eric from PythonWin since Eric looks much better and
> I can't debug gui code in PythonWin. Other than that PythonWin is working
> fine.
>
> I can connect to a MySQL database with test code in C++/Qt or python/PyQt
> and I can pop up label widgets and stuff. So it would appear that Qt and
> PyQt are basically working. The Eric editor window seems to work fine, so I
> suppose QScintilla is working. I tried some of the networking demos that
> come with Qt. The loopback demo worked fine, as did the fortune
> client/server pair (using a port) but the secure socket client crashed (OS
> put up a message saying it had stopped working and would be shut down -
> typical Vista behavior). But the fortune client server worked on port 50765
> or some such, with no complaint from the firewall (which I have
> subsequently turned on again). Does that narrow it down at all?
>
> Does anyone have relevant test code that might be helpful here in isolating
> the problem? Or ideas of things to look at?
>
> Thanks,
>
> -Melissa
>
>
>
>
> _______________________________________________
> Eric mailing list
> Eric at riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/eric



-- 
Detlev Offenbach
detlev at die-offenbachs.de