Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4538015
By: fabioz
Not currently... there's a bug for that already at:
https://sourceforge.net/tracker/index.php?func=detailaid=1788406group_id=85796
atid=577329
You can as workarounds use pydev extensions
SourceForge.net wrote:
You can as workarounds use pydev extensions (where you can inspect things
from
the console using prints)
You can only doing this when debugging code that is running within Eclipse
and not when using the remote debugger, right?
Thanks,
Patrick Smith
--
View this
You can as workarounds use pydev extensions (where you can inspect
things
from
the console using prints)
You can only doing this when debugging code that is running within Eclipse
and not when using the remote debugger, right?
Actually, you can... if you do the settrace in the
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4538613
By: cyberco
can be found here (in the jython forum):
http://sourceforge.net/mailarchive/forum.php?thread_name=ca8dfa360709260013g3d58
301eo1e9b66967c35586f%40mail.gmail.comforum_name=jython-users
Fabio Zadrozny-2 wrote:
You can as workarounds use pydev extensions (where you can inspect
things
from
the console using prints)
You can only doing this when debugging code that is running within
Eclipse
and not when using the remote debugger, right?
Actually, you can... if
Hi Fabio,
Unfortunately, my last message didn't get through because the attachment was
too large. In any case, I changed the flags to 2 as you specified and then
redirected both stdout and stderr to text files.
I've attached them to this email. So you'll see (near the end) the
following stack
