Unfortunately, as I said, the user is not local to the machine. What I meant by this, is that they do not have a shell on the system, and do not have access to the AppServer output that I am aware of. That means no direct access to Cache/PSP without going through a web-browser. Print statements also don't suffice, because they don't have access to the AppServer console.
What would be ideal, is a link in the Error page, or under the Admin pages somewhere to view the PSP .py files. Furthermore, you raised a good point about the print statements, it would be useful to have a standard way to capture the print statement output and make it available too. -Stuart- > -----Original Message----- > From: Edmund Lian [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 25, 2002 9:46 AM > To: Stuart Donaldson > Cc: Webware Discussion (E-mail) > Subject: Re: [Webware-discuss] tools to debug PSP code? > > > > On 11/25/2002 12:12:01 PM Stuart wrote: > > >The trace back and fancy-trace back output can give some > clues on what the > >problem is, but you generally don't see enough of the > translated .py file > to > >sufficiently set the context. > > > >Is there an easy way to make this available for viewing? > > The compiled PSP .py files are in ~Cache/PSP > > Print statements are pretty useful too. > > ...Edmund. > ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
