Woop! Well spotted. This is completely correct. I see this: w.insert_code(self.print_prep, w.after_code_for(-2)) -> w.insert_code(self.print_prep, w.after_code_for(-1)) On line 293 of zbytecodehacks/VSExec.py Changing the -1 back to a -2 makes things work as expected. I have no idea what other effects that may have :o) Regards, Phil +----------------------------------+ | Phil Mayers, Network Support | | Centre for Computing Services | | Imperial College | +----------------------------------+ -----Original Message----- From: J M Cerqueira Esteves [mailto:jmce@artenumerica.com] Sent: 26 March 2001 15:50 To: zope@zope.org Subject: Re: [Zope] Bug in Zope 2.3.1b3 PythonScripts -> mishandling 'print'? On Mon, Mar 26, 2001 at 12:25:06PM +0100, Chris Withers wrote:

"Mayers, Philip J" wrote:

...

This also happens in Zope2.3.1b2

We've been experiencing that too: http://classic.zope.org:8080/Collector/2094/view

Both return container.id and x = container.id print x return printed work properly. Perhaps the problem is related to the handling of some objects by the code handling print statements. -- jmce: +351 919838775 ~ http://artenumerica.com/ ~ http://artenumerica.org/ _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )