Re: [Zope 2.11] KGS incomplete (Was: Stepping forward and going beta)
I wrote a small script to match the KGS against the current Zope/HEAD externals. The KGS is missing several zope.app modules that are used within Zope 2. What to do with them? WARN: KGS incomplete - BTrees not found WARN: KGS incomplete - ThreadedAsync not found WARN: KGS incomplete - ZEO not found WARN: KGS incomplete - ZODB not found WARN: KGS incomplete - ZopeUndo not found WARN: KGS incomplete - persistent not found WARN: KGS incomplete - transaction not found WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found Andreas --On 24. Dezember 2007 04:54:50 +0100 Andreas Jung <lists@zopyx.com> wrote:
Thanks for pointing this out. I think I need to work on a script to generate the textfiles for the externals in Zope 2 automatically from the KGS :->
Happy x-mas, Andreas
--On 23. Dezember 2007 22:17:10 +0100 Philipp von Weitershausen <philipp@weitershausen.de> wrote:
Andreas Jung wrote:
--On 18. Dezember 2007 21:53:55 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Andreas Jung wrote:
the Zope 2.11 beta phase has been delayed for while. The reason for holding but the release was Philipps and Hannos work on the
<http://svn.zope.org/Zope/branches/philikon-aq/>
branch. Unfortunately both can't work (lack of personal time) on the branch and finish it in the feature. So I propose to release Zope 2.11 beta 1 by the end of the year w/o this branch. Zope 2.11 would contain the Zope 3.4 and ZODB 3.8 with blob support as major new features.
Objections? Thoughts?
+1 btw. Is there an ETA for beta1?
During x-mas and new year..likely around December 29th. If you need some more days, let me know but I would like to push the beta 1 release asap.
Note that doing a beta isn't just releasing the branch as it is. You should update all externals to the current 3.4.x releases of the individual eggs as well. The KGS [1] maintained by Stephan Richter provides you with a list of the most recent releases (except that the latest ZODB 3.8.0 candidate [2] isn't in it, apparently)
Also please be careful not to add or remove packages arbitrarily from the externals. If I remember correctly, a while back somebody just copied the externals from the Zope 3 tree to Zope 2 and added a bunch of not-releasable software to Zope 2 and removed other stuff in the process.
[1] http://download.zope.org/zope3.4/versions.cfg [2] http://cheeseshop.python.org/pypi/ZODB3/3.8.0c1
-- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting
-- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote:
I wrote a small script to match the KGS against the current Zope/HEAD externals. The KGS is missing several zope.app modules that are used within Zope 2. What to do with them?
WARN: KGS incomplete - BTrees not found WARN: KGS incomplete - ThreadedAsync not found WARN: KGS incomplete - ZEO not found WARN: KGS incomplete - ZODB not found WARN: KGS incomplete - ZopeUndo not found WARN: KGS incomplete - persistent not found
Those packages all ship with ZODB. The 3.8 0c1 tag is current as of a week ago. I'm assuming the KGS lists the ZODB egg. ;)
WARN: KGS incomplete - transaction not found
That package will move out into its own tree after ZODB 3.8.x. Until then, it should be found under there.
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
Mostly fossils, I think: $ pwd /home/tseaver/projects/Zope-CVS/Zope-trunk/lib/python $ for pname in \ content_types \ event \ filerepresentation \ location \ mail \ rdb \ servicenames \ site \ size \ tests; do echo $pname find . -name "*.py" -o -name "*.zcml" \ | xargs grep "zope\.app\.$pname" done content_types event ./zope/component/interfaces.py: __module__ = 'zope.app.event.objectevent' ./zope/app/file/browser/file.py: <zope.app.event.objectevent.ObjectModifiedEvent object at ...> ./zope/lifecycleevent/__init__.py: __module__ = 'zope.app.event.objectevent' ./zope/lifecycleevent/__init__.py: __module__ = 'zope.app.event.objectevent' ./zope/lifecycleevent/__init__.py: __module__ = 'zope.app.event.objectevent' filerepresentation location mail rdb servicenames site ./zope/app/site/tests/test_deprecation.py: >>> import zope.app.site.tests.placefulsetup ./zope/app/site/tests/test_deprecation.py: >>> placefulsetup = zope.app.site.tests.placefulsetup ./zope/app/site/tests/test_deprecation.py: 'zope.app.site.tests.placefulsetup' ./zope/app/site/tests/__init__.py: "Import of PlacefulSetup from zope.app.site.testing is deprecated " size tests There is one (awful) doctest file (zope/app/authentication/browser/principalfolder.txt) which mentions one of those names, but the test is so foul it needs repairing anyway. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFHb8Vd+gerLs4ltQ4RAqn9AJwKY7tNh7+hjcHY7dO+3HfPz5dGSACfQ82V XynAC2Ap33BXm+cY12o+uAU= =tRVz -----END PGP SIGNATURE-----
--On 24. Dezember 2007 09:42:37 -0500 Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Jung wrote:
I wrote a small script to match the KGS against the current Zope/HEAD externals. The KGS is missing several zope.app modules that are used within Zope 2. What to do with them?
WARN: KGS incomplete - BTrees not found WARN: KGS incomplete - ThreadedAsync not found WARN: KGS incomplete - ZEO not found WARN: KGS incomplete - ZODB not found WARN: KGS incomplete - ZopeUndo not found WARN: KGS incomplete - persistent not found
Those packages all ship with ZODB. The 3.8 0c1 tag is current as of a week ago. I'm assuming the KGS lists the ZODB egg. ;)
Jup. No problem with them.
WARN: KGS incomplete - transaction not found
That package will move out into its own tree after ZODB 3.8.x. Until then, it should be found under there.
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
I kicked them. I created a test branch and adjusted the externals so far. zope.thread seems to be a broken (there is no _zope_thread.c file)...however had no time for further investigations. And the testrunner produces 9 errors...anyone with a fast idea about the reasons for the failures (before doing further investigations)? "/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError . Error in test testSetupLocale (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError . Error in test testSetupServers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError . Error in test testSetupStartupHandler (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError . Error in test testSetupZServerThreads (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError . Error in test testZopeRunConfigure (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ............................................................................................... Error in test test_log_record (zLOG.tests.test_logging.LoggingIntegrationTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError The following test left new threads behind: testABOR (zope.server.ftp.tests.test_ftpserver.Tests) New thread(s): [<_DummyThread(Dummy-36, started daemon)>, <_DummyThread(Dummy-37, started daemon)>] ............. Ran 5369 tests with 0 failures and 7 errors in 2 minutes 32.974 seconds. Running OFS.tests.testCopySupportEvents.EventLayer tests: Set up OFS.tests.testCopySupportEvents.EventLayer in 0.668 seconds. Running: .............. Ran 14 tests with 0 failures and 0 errors in 0.140 seconds. Running Testing.ZopeTestCase.layer.ZopeLite tests: Tear down OFS.tests.testCopySupportEvents.EventLayer in 0.006 seconds. Set up Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Running: .................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... ........................................................................................................................................................................ Ran 668 tests with 0 failures and 0 errors in 18.748 seconds. Running Testing.ZopeTestCase.testShoppingCart.ShoppingCartLayer tests: Set up Testing.ZopeTestCase.testShoppingCart.ShoppingCartLayer in 0.164 seconds. Running: ................ Ran 16 tests with 0 failures and 0 errors in 0.269 seconds. Running Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer tests: Tear down Testing.ZopeTestCase.testShoppingCart.ShoppingCartLayer in 0.002 seconds. Set up Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.005 seconds. Running: .................. Ran 18 tests with 0 failures and 0 errors in 0.064 seconds. Running Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer tests: Tear down Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.002 seconds. Set up Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Running: .. Ran 2 tests with 0 failures and 0 errors in 0.015 seconds. Running zope.formlib.tests.FormlibLayer tests: Tear down Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Set up zope.formlib.tests.FormlibLayer in 4.086 seconds. Running: ..... Ran 5 tests with 0 failures and 0 errors in 0.009 seconds. Running zope.testbrowser.tests.TestBrowserLayer tests: Tear down zope.formlib.tests.FormlibLayer in 0.005 seconds. Set up zope.testbrowser.tests.TestBrowserLayer Traceback (most recent call last): File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/testing/testrunner.py", line 1252, in run_layer setup_layer(options, layer, setup_layers) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/testing/testrunner.py", line 1377, in setup_layer layer.setUp() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/testing/functional.py", line 288, in setUp self.setup = FunctionalTestSetup(self.config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/testing/functional.py", line 194, in __init__ self.app = Debugger(self.db, config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/debug/debug.py", line 36, in __init__ config(config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/appsetup/appsetup.py", line 111, in config context = xmlconfig.file(file, context=context, execute=execute) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 610, in file include(context, name, package) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 546, in include processxmlfile(f, context) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 378, in processxmlfile parser.parse(src) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/opt/python-2.4.4/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 348, in end_element_ns self._cont_handler.endElementNS(pair, None) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 357, in endElementNS self.context.end() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 542, in end self.stack.pop().finish() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 690, in finish actions = self.handler(context, **args) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 546, in include processxmlfile(f, context) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 378, in processxmlfile parser.parse(src) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/opt/python-2.4.4/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 348, in end_element_ns self._cont_handler.endElementNS(pair, None) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 357, in endElementNS self.context.end() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 542, in end self.stack.pop().finish() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 690, in finish actions = self.handler(context, **args) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 546, in include processxmlfile(f, context) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 378, in processxmlfile parser.parse(src) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/opt/python-2.4.4/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 348, in end_element_ns self._cont_handler.endElementNS(pair, None) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 357, in endElementNS self.context.end() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 542, in end self.stack.pop().finish() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 689, in finish args = toargs(context, *self.argdata) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 1381, in toargs args[str(name)] = field.fromUnicode(s) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/fields.py", line 139, in fromUnicode value = self.context.resolve(name) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 182, in resolve mod = __import__(mname, *_import_chickens) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/authentication/session.py", line 28, in ? from zope.session.interfaces import ISession ZopeXMLConfigurationError: File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/testbrowser/ftests/ftesting.zcml", line 12.2-12.47 ZopeXMLConfigurationError: File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/authentication/configure.zcml", line 61.2-61.33 ZopeXMLConfigurationError: File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/authentication/session.zcml", line 6.2-10.8 ImportError: No module named session.interfaces Running zope.traversing.tests.layer.TraversingLayer tests: Set up zope.traversing.tests.layer.TraversingLayer Traceback (most recent call last): File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/testing/testrunner.py", line 1252, in run_layer setup_layer(options, layer, setup_layers) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/testing/testrunner.py", line 1377, in setup_layer layer.setUp() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/testing/functional.py", line 288, in setUp self.setup = FunctionalTestSetup(self.config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/testing/functional.py", line 194, in __init__ self.app = Debugger(self.db, config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/debug/debug.py", line 36, in __init__ config(config_file) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/appsetup/appsetup.py", line 111, in config context = xmlconfig.file(file, context=context, execute=execute) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 610, in file include(context, name, package) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 546, in include processxmlfile(f, context) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 378, in processxmlfile parser.parse(src) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/opt/python-2.4.4/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 348, in end_element_ns self._cont_handler.endElementNS(pair, None) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 357, in endElementNS self.context.end() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 542, in end self.stack.pop().finish() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 690, in finish actions = self.handler(context, **args) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 546, in include processxmlfile(f, context) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 378, in processxmlfile parser.parse(src) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/opt/python-2.4.4/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/opt/python-2.4.4/lib/python2.4/xml/sax/expatreader.py", line 348, in end_element_ns self._cont_handler.endElementNS(pair, None) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/xmlconfig.py", line 357, in endElementNS self.context.end() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 542, in end self.stack.pop().finish() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 689, in finish args = toargs(context, *self.argdata) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/config.py", line 1381, in toargs args[str(name)] = field.fromUnicode(s) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/configuration/fields.py", line 141, in fromUnicode raise schema.ValidationError(v) ZopeXMLConfigurationError: File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/traversing/tests/ftesting.zcml", line 20.2-20.64 ZopeXMLConfigurationError: File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/python/zope/app/securitypolicy/meta.zcml", line 3.2-3.60 ConfigurationError: ('Invalid value for', 'package', 'ImportError: Module zope has no global securitypolicy') Andreas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote:
--On 24. Dezember 2007 09:42:37 -0500 Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Jung wrote:
I wrote a small script to match the KGS against the current Zope/HEAD externals. The KGS is missing several zope.app modules that are used within Zope 2. What to do with them?
WARN: KGS incomplete - BTrees not found WARN: KGS incomplete - ThreadedAsync not found WARN: KGS incomplete - ZEO not found WARN: KGS incomplete - ZODB not found WARN: KGS incomplete - ZopeUndo not found WARN: KGS incomplete - persistent not found Those packages all ship with ZODB. The 3.8 0c1 tag is current as of a week ago. I'm assuming the KGS lists the ZODB egg. ;)
Jup. No problem with them.
WARN: KGS incomplete - transaction not found That package will move out into its own tree after ZODB 3.8.x. Until then, it should be found under there.
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
I kicked them.
I created a test branch and adjusted the externals so far.
zope.thread seems to be a broken (there is no _zope_thread.c file)...however had no time for further investigations.
$ svn log $ZSVN/zope.thread/trunk ... - ------------------------------------------------------------------------ r77840 | jim | 2007-07-13 06:52:26 -0400 (Fri, 13 Jul 2007) | 1 line Removed unneeded C extension. This package is obsolete ... So, just remove anything in Zope's setup.py which is trying to build the C extension. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFHb92Y+gerLs4ltQ4RAj33AJwNOt5DlFAGoyMDGpc+w/GSIK73WgCgtJ8F yVa3eEmUS0H9dhtUHzmvG5Y= =UMBh -----END PGP SIGNATURE-----
On 24 Dec 2007, at 16:32 , Andreas Jung wrote:
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
I kicked them.
Well, they've been deprecated for a while but it says they were scheduled for removal in Zope 3.5 which corresponds Zope 2.12. So we can't get rid of them just yet. Zope 2.11 shoudl still contain them. IMO it's fine to simply leave the externals from the 2.10 branch for them in place.
I created a test branch and adjusted the externals so far.
zope.thread seems to be a broken (there is no _zope_thread.c file)...however had no time for further investigations.
As Tres pointed out, the C extension is gone, so you can just remove that entry from setup.py.
And the testrunner produces 9 errors...anyone with a fast idea about the reasons for the failures (before doing further investigations)?
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ...
I can say nothing about these failures. It seems like they're ZConfig- related.
Running zope.testbrowser.tests.TestBrowserLayer tests: Tear down zope.formlib.tests.FormlibLayer in 0.005 seconds. Set up zope.testbrowser.tests.TestBrowserLayer Traceback (most recent call last): ... ImportError: No module named session.interfaces
Running zope.traversing.tests.layer.TraversingLayer tests: Set up zope.traversing.tests.layer.TraversingLayer Traceback (most recent call last): ... ConfigurationError: ('Invalid value for', 'package', 'ImportError: Module zope has no global securitypolicy')
Those two are related to an unplanned split-up of zope.app.securitypolicy and zope.app.session. They occurred in the 3.4.x line even though they should've in the 3.5.x line. So, what you'll need to do is add externals for zope.session and zope.securitypolicy (notice the missing "app"!) according to the KGS. That should get that settled. Thanks for tackling this, Andreas. Merry Christmas, Philipp
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ...
I can say nothing about these failures. It seems like they're ZConfig-related.
Jup. But I could not figure the issue so far..anyway appears as a minor issue for me so far.
Those two are related to an unplanned split-up of zope.app.securitypolicy and zope.app.session. They occurred in the 3.4.x line even though they should've in the 3.5.x line. So, what you'll need to do is add externals for zope.session and zope.securitypolicy (notice the missing "app"!) according to the KGS. That should get that settled.
Jup. In addition zope.minmax has to be added. Because the ZConfig issue (see above) is the only problem so far, I've moved my branch and made it the official 2.11 branch: <http://svn.zope.org/Zope/branches/2.11/> I'll wrap it as a gift and release it over the weekend. Your-friendly-svn:externals-manager, Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting
On 25 Dec 2007, at 10:58 , Andreas Jung wrote:
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ...
I can say nothing about these failures. It seems like they're ZConfig-related.
Jup. But I could not figure the issue so far..anyway appears as a minor issue for me so far.
Should still be dealt with before going final nevertheless...
Those two are related to an unplanned split-up of zope.app.securitypolicy and zope.app.session. They occurred in the 3.4.x line even though they should've in the 3.5.x line. So, what you'll need to do is add externals for zope.session and zope.securitypolicy (notice the missing "app"!) according to the KGS. That should get that settled.
Jup. In addition zope.minmax has to be added.
Because the ZConfig issue (see above) is the only problem so far, I've moved my branch and made it the official 2.11 branch:
Cool! We should probably put the same set of externals on the trunk as well...
I'll wrap it as a gift and release it over the weekend.
/me lights the Christmas tree and cracks a few walnuts... Philipp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp von Weitershausen wrote:
On 25 Dec 2007, at 10:58 , Andreas Jung wrote:
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ... I can say nothing about these failures. It seems like they're ZConfig-related. Jup. But I could not figure the issue so far..anyway appears as a minor issue for me so far.
Should still be dealt with before going final nevertheless...
The tests expose some brokenness related to the global regsitries maintained by the Python logging module. I *strongly* doubt that test for emptying those registries is sane, at this point (those registries are insane, to start with). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFHdBjL+gerLs4ltQ4RAjJGAKCgkbA6bn8t7gcyI0Vnjd2Tq8TtTwCfQnB+ b/Uo6ABJ7aDzPkU7HTZdiHs= =3GoU -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp von Weitershausen wrote:
On 25 Dec 2007, at 10:58 , Andreas Jung wrote:
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ... I can say nothing about these failures. It seems like they're ZConfig-related. Jup. But I could not figure the issue so far..anyway appears as a minor issue for me so far.
Should still be dealt with before going final nevertheless...
I've just checked in a change which makes those errors go away: essentially, one test was leaving garbage log handlers around. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFHdXuS+gerLs4ltQ4RAvUTAKDLygTBLk8boUXNI8AjSUagG7gEiQCcCz1q 2M5qhZbikSOOGSP951dI1EQ= =JvjM -----END PGP SIGNATURE-----
--On 28. Dezember 2007 17:41:23 -0500 Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Philipp von Weitershausen wrote:
On 25 Dec 2007, at 10:58 , Andreas Jung wrote:
"/opt/python-2.4.4/bin/python" "/Users/ajung_data/sandboxes/Zope/ ajung-2-11-prep-branch/test.py" -v Running tests at level 1 Running unit tests: Running: .......... rror in test testSetupConfiguredLoggers (Zope2.Startup.tests.testStarter.ZopeStarterTestCase) Traceback (most recent call last): File "/opt/python-2.4.4/lib/python2.4/unittest.py", line 270, in run self.tearDown() File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/Zope2/Startup/tests/testStarter.py", line 69, in tearDown test_logger.LoggingTestBase.tearDown(self) File "/Users/ajung_data/sandboxes/Zope/ajung-2-11-prep-branch/lib/ python/ZConfig/components/logger/tests/test_logger.py", line 72, in tearDown assert loghandler._reopenable_handlers == [] AssertionError ... I can say nothing about these failures. It seems like they're ZConfig-related. Jup. But I could not figure the issue so far..anyway appears as a minor issue for me so far.
Should still be dealt with before going final nevertheless...
I've just checked in a change which makes those errors go away: essentially, one test was leaving garbage log handlers around.
Thanks Tres for your latest fixes. Andreas
Philipp von Weitershausen wrote:
On 24 Dec 2007, at 16:32 , Andreas Jung wrote:
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
I kicked them.
Well, they've been deprecated for a while but it says they were scheduled for removal in Zope 3.5 which corresponds Zope 2.12. So we can't get rid of them just yet. Zope 2.11 shoudl still contain them.
IMO it's fine to simply leave the externals from the 2.10 branch for them in place.
Now all of those above packages aren't in the beta1 tarball. I'd consider this a bug, right? Hanno
--On 28. Dezember 2007 17:56:20 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Philipp von Weitershausen wrote:
On 24 Dec 2007, at 16:32 , Andreas Jung wrote:
WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found
I kicked them.
Well, they've been deprecated for a while but it says they were scheduled for removal in Zope 3.5 which corresponds Zope 2.12. So we can't get rid of them just yet. Zope 2.11 shoudl still contain them.
IMO it's fine to simply leave the externals from the 2.10 branch for them in place.
Now all of those above packages aren't in the beta1 tarball. I'd consider this a bug, right?
I removed the externals so they are not in the b1 tarball. Possibly a bug from the deprecation point of view. On the other side it is hard enough now to keep track of the "right" version and dealing with the different versions. The KGS is a good start and I wrote a small script keeping the Zope 2 svn:externals in sync (mostly) with the KGS. However I need some additional metadata in order to know what deprecates when in order for having a half-way automated mechanism for updating the externals. I can not depend on the informal information coming from mailing lists and private mail becomes the huge amount of externals becomes unmanageable. The idea would be to extend the KGS or maintain a database/file that contains for every component its deprecation release (and perhaps other metadata needed). Thoughts? Andreas
Andreas Jung wrote:
--On 28. Dezember 2007 17:56:20 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Now all of those above packages aren't in the beta1 tarball. I'd consider this a bug, right?
I removed the externals so they are not in the b1 tarball. Possibly a bug from the deprecation point of view. On the other side it is hard enough now to keep track of the "right" version and dealing with the different versions. The KGS is a good start and I wrote a small script keeping the Zope 2 svn:externals in sync (mostly) with the KGS. However I need some additional metadata in order to know what deprecates when in order for having a half-way automated mechanism for updating the externals. I can not depend on the informal information coming from mailing lists and private mail becomes the huge amount of externals becomes unmanageable. The idea would be to extend the KGS or maintain a database/file that contains for every component its deprecation release (and perhaps other metadata needed).
Adding those deprecated but still functional packages to the KGS would be one way, but seems to be a bit of work. What about just adding a simple extra text file next to the generate_externals script which includes the paths to the deprecated packages. It's quite unlikely that any of them will see a new release anymore and thus need any adjustments. All that would happen is that the paths found in the extra file were added to the externals. On the 2.11 branch of Zope it would contain the deprecated packages in questions, whereas it would be empty on Zope trunk. Hanno
--On 29. Dezember 2007 08:17:43 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Andreas Jung wrote:
--On 28. Dezember 2007 17:56:20 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Now all of those above packages aren't in the beta1 tarball. I'd consider this a bug, right?
I removed the externals so they are not in the b1 tarball. Possibly a bug from the deprecation point of view. On the other side it is hard enough now to keep track of the "right" version and dealing with the different versions. The KGS is a good start and I wrote a small script keeping the Zope 2 svn:externals in sync (mostly) with the KGS. However I need some additional metadata in order to know what deprecates when in order for having a half-way automated mechanism for updating the externals. I can not depend on the informal information coming from mailing lists and private mail becomes the huge amount of externals becomes unmanageable. The idea would be to extend the KGS or maintain a database/file that contains for every component its deprecation release (and perhaps other metadata needed).
Adding those deprecated but still functional packages to the KGS would be one way, but seems to be a bit of work.
I just wonder what deprecation in the future means. There were some discussions about the "Zope 3 app server" and its future releases..one thought was that there would be no further releases of the Zope 3 app server but only independent releases of its modules. So each module has its individual lifecycle and no Zope 3 app server distro will give us the information that a particular module is deprecated. However a component zope.mod1 could use zope.mod2 within some release and deprecate the use of zope.mod2 at some point in the future...this thought alone lets me shiver :-) Back to the original problem, the zope.app.* modules. If those modules are used by Zope 2 internally only then we don't need to include them. If third-party products depend on zope.app (I have no idea if this is the case) then we must put them back...however there is a chance that these older zope.app modules produce errors during the tests because of possibly incompatibilities with newer modules. I have the strong opinion that zope.app is "something Zope internal" that should only be used by Zope 2/3 internal functionality and not by third-party apps...but perhaps I am wrong...no idea. Andreas
Andreas Jung wrote:
--On 29. Dezember 2007 08:17:43 +0100 Hanno Schlichting <plone@hannosch.info> wrote:
Adding those deprecated but still functional packages to the KGS would be one way, but seems to be a bit of work.
I just wonder what deprecation in the future means. There were some discussions about the "Zope 3 app server" and its future releases..one thought was that there would be no further releases of the Zope 3 app server but only independent releases of its modules. So each module has its individual lifecycle and no Zope 3 app server distro will give us the information that a particular module is deprecated. However a component zope.mod1 could use zope.mod2 within some release and deprecate the use of zope.mod2 at some point in the future...this thought alone lets me shiver :-)
I don't feel in any position to predict how this story will turn out. For Zope 2.11 it is mostly a non-issue. Let's talk about it when we start making plans for Zope 2.12.
Back to the original problem, the zope.app.* modules. If those modules are used by Zope 2 internally only then we don't need to include them. If third-party products depend on zope.app (I have no idea if this is the case) then we must put them back...
I only stumbled upon this whole problem because a plone.* package was using "from zope.app.event" which in Zope 2.10 gave a deprecation warning about removal in 3.5 but in 2.11 was suddenly gone. On Plone trunk aka 4.0 the import was already made conditional, so both zope.app.event and zope.event are tried. The underlying problem here is that a lot of the things in the zope.app namespace aren't really Zope App server specific and really should be in the zope.* namespace in order to make them reusable. We have done that move for quite a lot of packages already, but aren't anywhere near finished. Anyone tried to use zope.formlib without zope.app.form for example?
however there is a chance that these older zope.app modules produce errors during the tests because of possibly incompatibilities with newer modules. I have the strong opinion that zope.app is "something Zope internal" that should only be used by Zope 2/3 internal functionality and not by third-party apps...but perhaps I am wrong...no idea.
I think your idea has merit and could be a goal when we started over again, but what we have today in zope.app isn't anywhere near that goal. The number of imports from zope.app inside Plone are numerous, as a lot of functionality is hidden in those packages. Hanno
participants (4)
-
Andreas Jung -
Hanno Schlichting -
Philipp von Weitershausen -
Tres Seaver