[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Martijn Faassen wrote: Okay, so we can safely add Chris (and also Philipp) to the list of people maintaining our windows binary eggs. Awesome! Chris, do you think you can take it from here in getting an environment set up? Would be rgeat to have a bullet point list for how to get a suitable environment set up given that I don't have mingw32 and have never used it before in my life :-S I've pointed you at the Windows section in http://plone.org/documentation/tutorial/buildout/prerequisites at least once now. Maybe you'll manage to swallow your aversion to Plone and read it this time? It really isn't hard at all. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Sidnei da Silva wrote: On Fri, Jul 18, 2008 at 1:23 PM, Chris Withers <[EMAIL PROTECTED]> wrote: Would be rgeat to have a bullet point list for how to get a suitable environment set up given that I don't have mingw32 and have never used it before in my life :-S Like this? http://plone.org/documentation/how-to/using-ploneout-on-windows But I'm alergic to things with plohn in the title <0.5 wink> That's why I posted you the link to the tutorial from Phillip as well, so even if you'd look into mine, you wouldn't have to admit it ;) Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Martijn Faassen wrote: Okay, so we can safely add Chris (and also Philipp) to the list of people maintaining our windows binary eggs. Awesome! Chris, do you think you can take it from here in getting an environment set up? Would be rgeat to have a bullet point list for how to get a suitable environment set up given that I don't have mingw32 and have never used it before in my life :-S There are too tutorials out there: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_07_26_cheap-binary-windows is the simple version. http://plone.org/documentation/how-to/using-ploneout-on-windows Is the more detailed one including screenshots... Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Martin Aspeli wrote: Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. I would expect the above to work as *everything* is built using mingw32. No, it is not. It uses the official Python Windows installer, being built with some M$ C compiler, adds Python Win32 add-ons and PIL using the Windows binary installers and only advertises using MinGW for compiling all of Zope itself. I haven't seen anyone running into any problems with this approach for years now. From my understanding starting with 2.4 Python includes certain files to make this approach work as smooth as possible. In the old days you had to extract some header files out of the dll's, which are now included in the binary installers by default. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Martin Aspeli wrote: Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. I'm not sure if you're deliberately missing my point here ;-) I would expect the above to work as *everything* is built using mingw32. I'm asking what happens if python is built using whatever the official python releases are built with but the c extensions we provide are built with mingw32? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Stephan Richter wrote: On Saturday 12 July 2008, Martijn Faassen wrote: Chris wants to do them, he just wants some documentation on how to get started, I suspect. I use Philipp's blog entry from ages ago: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_07_26_cheap-binary-windows You see, I've always worried about using mingw32. I was under the impression that you really wanted to have all the C bits compiled with the same compiler, and I know that the official Python 2.5 releases aren't compiled with mingw32... Can someone with definitive knowledge let us know if there can be problems when some C-extensions are compiled with mingw32 and others (including python itself!) are compiled with the appropriate microsoft compiler? Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Lorenzo Gil Sánchez wrote: I tried to go further and discover the source of this problem adding a breakpoint just before the exception is raised. This is what I got: (Pdb) self.context (Pdb) self.context.keys() (Pdb) tuple(self.context.keys()) *** MemoryError: I just committed a fix to the trunk of zope.proxy, zope.security, and zope.app.container. They all needed the Py_ssize_t conversion as described by PEP 353. Without the conversion, Python extensions running under 64 bit Python 2.5 tend to break with MemoryErrors. The MemoryErrors are caused by C code filling only 4 bytes of an 8 byte length value; the remaining 4 bytes end up with random junk, leading various code to believe the extension wants to allocate far more memory than it actually needs. We might want to backport the fix, but I don't know which branches are being maintained. Shane ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: > Martijn Faassen wrote: > >> Tres, could you report this issue on Launchpad? > > Once we establish what the problem is for sure. > >> Not Lorenzo's issue as it happens with an empty container, but perhaps >> we can work out a bug report for the ZODB folks as well. Just dig into >> what's up in .values() or .items() and where the error exactly occurs, >> perhaps this way we can come up with a very small ZODB sample >> application. > > One thing I notice right away: the ZODB egg pulled from PyPI is: > 'ZODB3-3.9.0_dev_r77011'. We have *got* to get people to quit > "releasing" such eggs to the unsuspecting public. Anybody who needs > such a distribution should be able to build it from subversion, or else > package it themselves and put it in a "private" location. > > I guess this package was found at http://download.zope.org/distribution. > I imagine that 'zopeproject' should use a buildout.cfg which points at > a sane index (e.g., the KGS), and *doesn't* use 'find-links' at all Another issue: when running 'zopeproject' as Lorenzo described on my machine, the target environment ends up actually wiring in a Python $ cd /tmp $ /usr/bin/python2.5 /path/to/virtualenv.py --no-site-packages lgs2.5 ... $ cd /tmp/lgs2.5 $ bin/python -V Python 2.5.2 $ bin/easy_install zopeproject ... $ head -1 bin/paster #!/tmp/lgs2.5/bin/python $ bin/zopeproject HelloWorld ... $ head -1 HelloWorld/bin/paster #!/home/tseaver/projects/Zope-CVS/bin/python2.4 Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIe1yP+gerLs4ltQ4RAue9AKDIlt5F8uMmNjWqnj+wt0pxKhGz1wCfU4Om i/c08sGUyhdSx3+l+xftqsA= =nrnm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: > Tres, could you report this issue on Launchpad? Once we establish what the problem is for sure. > Not Lorenzo's issue as it happens with an empty container, but perhaps > we can work out a bug report for the ZODB folks as well. Just dig into > what's up in .values() or .items() and where the error exactly occurs, > perhaps this way we can come up with a very small ZODB sample > application. One thing I notice right away: the ZODB egg pulled from PyPI is: 'ZODB3-3.9.0_dev_r77011'. We have *got* to get people to quit "releasing" such eggs to the unsuspecting public. Anybody who needs such a distribution should be able to build it from subversion, or else package it themselves and put it in a "private" location. I guess this package was found at http://download.zope.org/distribution. I imagine that 'zopeproject' should use a buildout.cfg which points at a sane index (e.g., the KGS), and *doesn't* use 'find-links' at all Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIe1ph+gerLs4ltQ4RAmkdAJ9sgZoSwOd4XlpI0tr4rTP+651bAwCggM4K YB/n6d8TDP73PtiMqwFctak= =As1K -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
I have reported Bug 248380: on this issue. The problem seems to me to be in building the .c modules. That causes the MemoryError that Lorenzo reported but it isn't the root of the problem. There are a large number of "warning: initialization from incompatible pointer type" issues. --Tim On Mon, 2008-07-14 at 13:30 +0200, Martijn Faassen wrote: > Hi there, > > Tres, could you report this issue on Launchpad? > > Not Lorenzo's issue as it happens with an empty container, but perhaps > we can work out a bug report for the ZODB folks as well. Just dig into > what's up in .values() or .items() and where the error exactly occurs, > perhaps this way we can come up with a very small ZODB sample > application. > > Regards, > > Martijn > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) -- ** Join the OSHIP project. It is the standards based, open source healthcare application platform in Python. Home page: https://launchpad.net/oship/ Wiki: http://www.openehr.org/wiki/display/dev/Python+developer%27s+page ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Hi there, Tres, could you report this issue on Launchpad? Not Lorenzo's issue as it happens with an empty container, but perhaps we can work out a bug report for the ZODB folks as well. Just dig into what's up in .values() or .items() and where the error exactly occurs, perhaps this way we can come up with a very small ZODB sample application. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
El dom, 13-07-2008 a las 09:35 -0400, Tres Seaver escribió: > -BEGIN PGP SIGNED MESSAGE- > > > > > > Steps to reproduce this problem: > > > > virtualenv --no-site-packages z3env25 > > cd z3env25 > > . bin/activate > > easy_install zopeproject > > zopeproject HelloWorld > > cd HelloWorld > > bin/paster serve deploy.ini > > > > > > I tried to go further and discover the source of this problem adding a > > breakpoint just before the exception is raised. This is what I got: > > > > (Pdb) self.context > > > > (Pdb) self.context.keys() > > > > (Pdb) tuple(self.context.keys()) > > *** MemoryError: > > (Pdb) self.context.values() > > > > (Pdb) tuple(self.context.values()) > > *** MemoryError: > > > > So, it may be a ZODB issue. > > Your container has too many items in it: the 'keys', 'items', and > 'values' methods of the BTree classes all return generators for exactly > this reason. As I described in the steps to reproduce the problem, this happens in an **empty** ZODB with no items in the root container. The url that was published when the memory error was raised was http://127.0.0.1:8080/ Lorenzo ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: > Lorenzo Gil Sánchez wrote: >> Here is the traceback information: > >> 2008-07-13T10:44:37 ERROR SiteError http://127.0.0.1:8080/@@index.html >> Traceback (most recent call last): >> File >> "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", >> line 133, in publish >> File >> "/home/lgs/z3env25/eggs/tmpaC6Rf5/zope.app.publication-3.4.3-py2.5.egg/zope/app/publication/zopepublication.py", >> line 167, in callObject >> File >> "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", >> line 108, in mapply >>- __traceback_info__: > > >> File >> "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", >> line 114, in debug_call >> File >> "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", >> line 443, in index >> File >> "/home/lgs/z3env25/eggs/tmp6KzCKG/zope.app.pagetemplate-3.4.0-py2.5.egg/zope/app/pagetemplate/viewpagetemplatefile.py", >> line 83, in __call__ >> File >> "/home/lgs/z3env25/eggs/tmp6KzCKG/zope.app.pagetemplate-3.4.0-py2.5.egg/zope/app/pagetemplate/viewpagetemplatefile.py", >> line 51, in __call__ >> File >> "/home/lgs/z3env25/eggs/tmprTDkjU/zope.pagetemplate-3.4.0-py2.5.egg/zope/pagetemplate/pagetemplate.py", >> line 115, in pt_render >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 271, in __call__ >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 888, in do_useMacro >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 533, in do_optTag_tal >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 518, in do_optTag >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 513, in no_tag >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 858, in do_defineMacro >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 954, in do_defineSlot >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 946, in do_defineSlot >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 343, in interpret >> File >> "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", >> line 819, in do_loop_tal >> File >> "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/tales.py", >> line 682, in setRepeat >> File >> "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/tales.py", >> line 696, in evaluate > >> - >> /home/lgs/z3env25/eggs/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/index.pt >>- Line 36, Column 6 >>- Expression: >>- Names: >> {'args': (), >>'context': > 0x7f0b7e9762a8>, >>'default': , >>'loop': {}, >>'nothing': None, >>'options': {}, >>'repeat': {}, >>'request': > URL=http://127.0.0.1:8080/@@index.html>, >>'template': >> > at 0x7f0b8122d110>, >>'view': > 0x7f0b7de06990>, >>'views': > object at 0x7f0b7de06a10>} >> File >> "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/expressions.py", >> line 217, in __call__ >> File >> "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/expressions.py", >> line 211, in _eval >> File >> "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", >> line 97, in listContentInfo >> File >> "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", >> line 123, in _normalListContentsInfo >> MemoryError > > >> Steps to reproduce this problem: > >> virtualenv --no-site-packages z3env25 >> cd z3env25 >> . bin/activate >> easy_install zopeproject >> zopeproject HelloWorld >> cd HelloWorld >> bin/
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lorenzo Gil Sánchez wrote: > Here is the traceback information: > > 2008-07-13T10:44:37 ERROR SiteError http://127.0.0.1:8080/@@index.html > Traceback (most recent call last): > File > "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", > line 133, in publish > File > "/home/lgs/z3env25/eggs/tmpaC6Rf5/zope.app.publication-3.4.3-py2.5.egg/zope/app/publication/zopepublication.py", > line 167, in callObject > File > "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", > line 108, in mapply >- __traceback_info__: > > File > "/home/lgs/z3env25/eggs/tmpbLKU14/zope.publisher-3.5.3-py2.5.egg/zope/publisher/publish.py", > line 114, in debug_call > File > "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", > line 443, in index > File > "/home/lgs/z3env25/eggs/tmp6KzCKG/zope.app.pagetemplate-3.4.0-py2.5.egg/zope/app/pagetemplate/viewpagetemplatefile.py", > line 83, in __call__ > File > "/home/lgs/z3env25/eggs/tmp6KzCKG/zope.app.pagetemplate-3.4.0-py2.5.egg/zope/app/pagetemplate/viewpagetemplatefile.py", > line 51, in __call__ > File > "/home/lgs/z3env25/eggs/tmprTDkjU/zope.pagetemplate-3.4.0-py2.5.egg/zope/pagetemplate/pagetemplate.py", > line 115, in pt_render > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 271, in __call__ > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 888, in do_useMacro > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 533, in do_optTag_tal > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 518, in do_optTag > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 513, in no_tag > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 858, in do_defineMacro > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 954, in do_defineSlot > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 946, in do_defineSlot > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 343, in interpret > File > "/home/lgs/z3env25/eggs/tmpjL9hPq/zope.tal-3.5.0-py2.5.egg/zope/tal/talinterpreter.py", > line 819, in do_loop_tal > File > "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/tales.py", > line 682, in setRepeat > File > "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/tales.py", > line 696, in evaluate > > - > /home/lgs/z3env25/eggs/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/index.pt >- Line 36, Column 6 >- Expression: >- Names: > {'args': (), >'context': 0x7f0b7e9762a8>, >'default': , >'loop': {}, >'nothing': None, >'options': {}, >'repeat': {}, >'request': URL=http://127.0.0.1:8080/@@index.html>, >'template': > at 0x7f0b8122d110>, >'view': 0x7f0b7de06990>, >'views': object at 0x7f0b7de06a10>} > File > "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/expressions.py", > line 217, in __call__ > File > "/home/lgs/z3env25/eggs/tmpXUllta/zope.tales-3.4.0-py2.5.egg/zope/tales/expressions.py", > line 211, in _eval > File > "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", > line 97, in listContentInfo > File > "/home/lgs/z3env25/eggs/tmp8cmA1c/zope.app.container-3.6.0-py2.5-linux-x86_64.egg/zope/app/container/browser/contents.py", > line 123, in _normalListContentsInfo > MemoryError > > > Steps to reproduce this problem: > > virtualenv --no-site-packages z3env25 > cd z3env25 > . bin/activate > easy_install zopeproject > zopeproject HelloWorld > cd HelloWorld > bin/paster serve deploy.ini > > > I tried to go further and discover the source of this problem adding a > breakpoint just before the exception is