I'm no doubt missing something silly, but Ape 0.6 worked and now 0.7 is giving me troubles. Here's the specifics: Zope 2.6.2b4 on RH Linux 9. I have Ape 0.7 and DBTab 1.2 installed. and actually, Zope starts up fine if I remove the DBTab.conf and custom_zodb.py files from my instance root. WITH those files configured according to the instructions (pretty much the defaults) though, I get the following traceback when starting Zope: 2003-08-13T15:22:49 PANIC(300) z2 Startup exception Traceback (innermost last): File /usr/local/zope/Zope/z2.py, line 585, in ? File /usr/local/zope/Zope/lib/python/Zope/__init__.py, line 46, in startup (Object: startup) File /usr/local/zope/Zope/lib/python/Zope/App/startup.py, line 56, in startup File /usr/local/zope/Zope/custom_zodb.py, line 19, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/MainConfiguration.py, line 29, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 260, in __init__ File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 392, in _readConfig File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 93, in setStorageParams File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/setup/dbtab.py, line 24, in convertApeStorageArgs File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zodb3/db.py, line 42, in callMapperFactory File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 52, in createFSMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 38, in createMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 485, in wireMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 112, in read File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/__init__.py, line 31, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 109, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/xmlreader.py, line 123, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 216, in feed File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 312, in start_element File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 97, in startElement File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 192, in handle_serializer NameError: global name 'handle_component' is not defined anyone have a clue what I managed to break? thanks- Larry
On Wed, 13 Aug 2003 15:24:24 -0400, Larry J. C. Prikockis wrote:
I'm no doubt missing something silly, but Ape 0.6 worked and now 0.7 is giving me troubles.
Here's the specifics: Zope 2.6.2b4 on RH Linux 9. I have Ape 0.7 and DBTab 1.2 installed. and actually, Zope starts up fine if I remove the DBTab.conf and custom_zodb.py files from my instance root.
WITH those files configured according to the instructions (pretty much the defaults) though, I get the following traceback when starting Zope:
2003-08-13T15:22:49 PANIC(300) z2 Startup exception Traceback (innermost last): File /usr/local/zope/Zope/z2.py, line 585, in ? File /usr/local/zope/Zope/lib/python/Zope/__init__.py, line 46, in startup (Object: startup) File /usr/local/zope/Zope/lib/python/Zope/App/startup.py, line 56, in startup File /usr/local/zope/Zope/custom_zodb.py, line 19, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/MainConfiguration.py, line 29, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 260, in __init__ File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 392, in _readConfig File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 93, in setStorageParams File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/setup/dbtab.py, line 24, in convertApeStorageArgs File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zodb3/db.py, line 42, in callMapperFactory File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 52, in createFSMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 38, in createMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 485, in wireMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 112, in read File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/__init__.py, line 31, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 109, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/xmlreader.py, line 123, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 216, in feed File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 312, in start_element File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 97, in startElement File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 192, in handle_serializer NameError: global name 'handle_component' is not defined
anyone have a clue what I managed to break? thanks- Larry
well, I answered my own question this time... turns out the problem relates to statically nested scopes... apeconf.py apparently works just fine in python 2.2+, but fails in 2.1.x unless the nest_scope option is turned on (it's standard in 2.2). An addition of "from __future__ import nested_scope" to the top of apeconf.py fixes it nicely for 2.1. works like a charm now! -Larry p.s. Shane- I'm guessing you're running Zope 2.6.x on the "unsupported" Python 2.2? :-)
On Thu, 14 Aug 2003, Larry J. C. Prikockis wrote:
well, I answered my own question this time... turns out the problem relates to statically nested scopes... apeconf.py apparently works just fine in python 2.2+, but fails in 2.1.x unless the nest_scope option is turned on (it's standard in 2.2).
An addition of "from __future__ import nested_scope" to the top of apeconf.py fixes it nicely for 2.1.
works like a charm now!
-Larry
p.s. Shane- I'm guessing you're running Zope 2.6.x on the "unsupported" Python 2.2? :-)
I've been testing with the Zope HEAD (almost Zope 2.7) on Python 2.2. Thanks for pointing this out. I forgot to test with Python 2.1. ;-) I expect to put out a 0.7.1 right away. Shane
On Wed, 13 Aug 2003 15:24:24 -0400, Larry J. C. Prikockis wrote:
I'm no doubt missing something silly, but Ape 0.6 worked and now 0.7 is giving me troubles.
Here's the specifics: Zope 2.6.2b4 on RH Linux 9. I have Ape 0.7 and DBTab 1.2 installed. and actually, Zope starts up fine if I remove the DBTab.conf and custom_zodb.py files from my instance root.
WITH those files configured according to the instructions (pretty much the defaults) though, I get the following traceback when starting Zope:
2003-08-13T15:22:49 PANIC(300) z2 Startup exception Traceback (innermost last): File /usr/local/zope/Zope/z2.py, line 585, in ? File /usr/local/zope/Zope/lib/python/Zope/__init__.py, line 46, in startup (Object: startup) File /usr/local/zope/Zope/lib/python/Zope/App/startup.py, line 56, in startup File /usr/local/zope/Zope/custom_zodb.py, line 19, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/MainConfiguration.py, line 29, in ? File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 260, in __init__ File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 392, in _readConfig File /usr/local/zope/Zope/lib/python/Products/DBTab/DBTab.py, line 93, in setStorageParams File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/setup/dbtab.py, line 24, in convertApeStorageArgs File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zodb3/db.py, line 42, in callMapperFactory File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 52, in createFSMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/zope2/mapper.py, line 38, in createMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 485, in wireMapper File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 112, in read File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/__init__.py, line 31, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 109, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/xmlreader.py, line 123, in parse File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 216, in feed File /usr/local/zope/Zope/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py, line 312, in start_element File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/common.py, line 97, in startElement File /usr/local/zope/Zope/lib/python/Products/Ape/lib/apelib/config/apeconf.py, line 192, in handle_serializer NameError: global name 'handle_component' is not defined
anyone have a clue what I managed to break? thanks- Larry
well, I answered my own question this time... turns out the problem relates to statically nested scopes... apeconf.py apparently works just fine in python 2.2+, but fails in 2.1.x unless the nest_scope option is turned on (it's standard in 2.2). An addition of "from __future__ import nested_scope" to the top of apeconf.py fixes it nicely for 2.1. works like a charm now! -Larry
participants (2)
-
Larry J. C. Prikockis -
Shane Hathaway