[Pydev-users] [pydev - Users] RE: Remote Debugging and stdout

2009-01-27 Thread SourceForge.net
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6277232 By: m_grimm Hi Fabio, that's it. with two print statements the first one comes out. Thanks, Markus __ You are receiving this ema

[Pydev-users] [pydev - Users] RE: Remote Debugging and stdout

2009-01-27 Thread SourceForge.net
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6274216 By: fabioz You're right... it should work there... What can be happening is that as print testVar is the last statement, and right after that the debugging ends, what can be happening is that the proces

[Pydev-users] [pydev - Users] RE: Remote Debugging and stdout

2009-01-27 Thread SourceForge.net
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6268932 By: m_grimm hm... redirecting the output? I don't know how... :)) It's a simple script like this: # -*- coding: utf-8 -*- import sys if __name__ == '__main__': sys.path.append("debug") print "

[Pydev-users] [pydev - Users] RE: Remote Debugging and stdout

2009-01-23 Thread SourceForge.net
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6227562 By: fabioz It appears fine to me... Have you checked if your application is not redirecting the output itself? If the application changes the stdout, pydev is not able to do that redirection. Cheers,