I'm getting a fair bit of messages like: Traceback (innermost last): File d:\local\src\Zope\lib\python\ZPublisher\Publish.py, line 860, in publish_module File d:\local\src\Zope\lib\python\ZPublisher\Publish.py, line 582, in publish (Info: /make_piechart) File d:\local\src\Zope\lib\python\Products\ExternalMethod\ExternalMethod.py, line 254, in __call__ (Object: Item) (Info: ((<Application instance at 0092CB70>, Response('')), {}, None)) TypeError: read-only character buffer, class when trying to look at images returned by external methods, in a frame which shows a 'broken picture' icon. What does it mean? --david
Here's a bit of weirdness for you. Today I compiled cDocumentTemplate and dropped it into a Python library to see what impact it would have on some very intensive DTML in an application of mine... and it actually *slowed down slightly*. I couldn't believe it, so I started doing all sorts of tests. I should note, however, that my 'pDocumentTemplate' has been patched to use the C version of MultiMapping from the ExtensionClass kit rather than the Python MultiMapping. Anyhow, here are some of the results: pDocumentTemplate: ~9 seconds of CPU cDocumentTemplate: ~12 seconds of CPU pDocumentTemplate + render_blocks from cDocumentTemplate: ~8 seconds of CPU Same, with -X option to Python: ~7 seconds of CPU I noticed that there were often dramatic differences in speed depending on whether -X was used. It seems that Python 1.5's class-based built-in exceptions can be hell on DocumentTemplates (and presumably upon Acquisition as well). Any ideas why cDocumentTemplate's InstanceDict and TemplateDict would run slower than the Python versions (given a C MultiMapping)?
participants (2)
-
David Ascher -
Phillip J. Eby