Using pylint v0.12.2 with PyScripter

[PyScripter]

To use the latest version of Pylint with Pyscripter you need to modify
the existing Pylint tool. Go to Tools, Configure Tools... and change

a) the parameters to
$[PythonDir-Short]Lib\site-packages\pylint\lint.py $[ActiveDoc-Short] -
f parseable
(pylint has change the format the parseable option)

and

b) blank out the Working directory. This is to prevent pylint from
omitting the file path from the output.

With these too simple chances pylint should work fine and you should
be able to click on the messages to jump to the error position.

[PieroJ]

On Feb 9, 5:49 am, "PyScripter" <pyscrip...@gmail.com> wrote:
> To use the latest version of Pylint with Pyscripter you need to modify
> the existing Pylint tool. Go to Tools, Configure Tools... and change
>

Great, thanks. I've got another one for you now. The remote wx
debugger seems to work some of the time when debugging scripts using
pylab (I'm still trying to track down exactly when it does work for
me), but I'm having real difficulty with full-blown wx applications.
For example, in the wxpython demo/documentation package there are a
few examples, the simplest of which is simple.py. When debugging this
I haven't been able to get the debugger to even stop at a breakpoint.
It starts the app ok, but the debugger seems to just exit (all the
debugger button in the toolbar go back to the non-debug state).

Maybe it's something to do with my setup: I'm running python 2.5 on
XP, with wxpython 2.8.1.1.

thanks very much!
Piero

[PyScripter]

Please see response in separate thread.

[PieroJ]

So it was just a case of incorrect expectations. Thanks for the
explanation, and apologies for the misunderstanding on my part.

Piero

[PyScripter]

So after the explanations are you now able to debug wxPython scripts
as you wanted? Is there any feature missing?

[PieroJ]

On Feb 12, 11:19 am, "PyScripter" <pyscrip...@gmail.com> wrote:
> So after the explanations are you now able to debug wxPython scripts
> as you wanted? Is there any feature missing?

Hi
I can now debug my wxPython GUI programs without problems using the
remote debugger (as long as I remember to reinitialize each time. This
doesn't seem to always be necessary, but it seems to be good
practice). I haven't been able to reproduce any of the unexpected
behaviour I saw before without, for example, using the wrong engine or
purposely not reinitializing for a few consecutive runs. So yes, I'd
say it works very well indeed, thank you!

In your explanation you say that Pyscripter with the wx engine
supports debugging of pylab scripts in interactive mode, in the same
way the IPython does. My interpretation of this is that I can debug a
script like this:

>>>import pylab
>>>pylab.ion()
>>>pylab.plot([1,2,3])
>>>pylab.figure()
>>>pylab.plot([6,7,8,9,0])

and line-by-line see the plots created and be able to interact with
them. But it looks like I got this wrong too, since the figures are
created but are not interactive. Could you please elaborate a little
more on this please?

I've also noticed the following:
A call to sys.exit() using the remote debugger in a wx GUI program
kills the socket connection and Pyscripter goes into a loop, the only
way out of which is to kill the process in Task Manager (probably
serves me right for not closing the app elegantly).
Breakpoints can't be disabled - program execution stops even when the
bullet in the editor is greyed out.

Finally, I think a keyboard shortcut for debugger reinitialization
would be really useful.

Piero

[Kiriakos Vlahos]

Thanks for the feedback!  See separate thread regarding running pylab in interactive mode.  I will add a shortcut to the reinitialize command in the next beta and I will try to handle sys.exit() more gracefully.

On 13/02/07, PieroJ <the.br...@tiscali.it> wrote: