[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/app/ - Adjust externals to released versions
Log message for revision 92593: - Adjust externals to released versions Changed: _U Zope/trunk/lib/python/zope/app/ -=- Property changes on: Zope/trunk/lib/python/zope/app ___ Name: svn:externals - annotation svn://svn.zope.org/repos/main/zope.app.annotation/tags/3.4.0/src/zope/app/annotation apidoc svn://svn.zope.org/repos/main/zope.app.apidoc/tags/3.4.3/src/zope/app/apidoc applicationcontrol svn://svn.zope.org/repos/main/zope.app.applicationcontrol/tags/3.4.1/src/zope/app/applicationcontrol appsetup svn://svn.zope.org/repos/main/zope.app.appsetup/tags/3.4.1/src/zope/app/appsetup authentication svn://svn.zope.org/repos/main/zope.app.authentication/tags/3.4.1/src/zope/app/authentication basicskin svn://svn.zope.org/repos/main/zope.app.basicskin/tags/3.4.0/src/zope/app/basicskin broken svn://svn.zope.org/repos/main/zope.app.broken/tags/3.4.0/src/zope/app/broken cache svn://svn.zope.org/repos/main/zope.app.cache/tags/3.4.0/src/zope/app/cache component svn://svn.zope.org/repos/main/zope.app.component/tags/3.5.0/src/zope/app/component container svn://svn.zope.org/repos/main/zope.app.container/tags/3.6.2/src/zope/app/container content svn://svn.zope.org/repos/main/zope.app.content/tags/3.4.0/src/zope/app/content debug svn://svn.zope.org/repos/main/zope.app.debug/tags/3.4.0/src/zope/app/debug dependable svn://svn.zope.org/repos/main/zope.app.dependable/tags/3.4.0/src/zope/app/dependable error svn://svn.zope.org/repos/main/zope.app.error/tags/3.5.1/src/zope/app/error exception svn://svn.zope.org/repos/main/zope.app.exception/tags/3.4.1/src/zope/app/exception file svn://svn.zope.org/repos/main/zope.app.file/tags/3.4.2/src/zope/app/file folder svn://svn.zope.org/repos/main/zope.app.folder/tags/3.4.0/src/zope/app/folder form svn://svn.zope.org/repos/main/zope.app.form/trunk/src/zope/app/form generations svn://svn.zope.org/repos/main/zope.app.generations/tags/3.4.1/src/zope/app/generations http svn://svn.zope.org/repos/main/zope.app.http/tags/3.4.1/src/zope/app/http i18n svn://svn.zope.org/repos/main/zope.app.i18n/tags/3.4.4/src/zope/app/i18n interface svn://svn.zope.org/repos/main/zope.app.interface/tags/3.4.0/src/zope/app/interface intid svn://svn.zope.org/repos/main/zope.app.intid/tags/3.4.1/src/zope/app/intid keyreference svn://svn.zope.org/repos/main/zope.app.keyreference/tags/3.4.1/src/zope/app/keyreference layers svn://svn.zope.org/repos/main/zope.app.layers/tags/3.4.0/src/zope/app/layers locales svn://svn.zope.org/repos/main/zope.app.locales/tags/3.4.1/src/zope/app/locales onlinehelp svn://svn.zope.org/repos/main/zope.app.onlinehelp/tags/3.4.1/src/zope/app/onlinehelp pagetemplate svn://svn.zope.org/repos/main/zope.app.pagetemplate/tags/3.4.0/src/zope/app/pagetemplate pluggableauth svn://svn.zope.org/repos/main/zope.app.pluggableauth/tags/3.4.0/src/zope/app/pluggableauth preference svn://svn.zope.org/repos/main/zope.app.preference/tags/3.4.1/src/zope/app/preference preview svn://svn.zope.org/repos/main/zope.app.preview/tags/3.4.0/src/zope/app/preview principalannotation svn://svn.zope.org/repos/main/zope.app.principalannotation/tags/3.4.0/src/zope/app/principalannotation publication svn://svn.zope.org/repos/main/zope.app.publication/tags/3.4.3/src/zope/app/publication publisher svn://svn.zope.org/repos/main/zope.app.publisher/trunk/src/zope/app/publisher renderer svn://svn.zope.org/repos/main/zope.app.renderer/tags/3.4.0/src/zope/app/renderer rotterdam svn://svn.zope.org/repos/main/zope.app.rotterdam/tags/3.4.1/src/zope/app/rotterdam schema svn://svn.zope.org/repos/main/zope.app.schema/tags/3.4.0/src/zope/app/schema security svn://svn.zope.org/repos/main/zope.app.security/tags/3.5.2/src/zope/app/security securitypolicy svn://svn.zope.org/repos/main/zope.app.securitypolicy/tags/3.4.6/src/zope/app/securitypolicy session svn://svn.zope.org/repos/main/zope.app.session/tags/3.5.1/src/zope/app/session skins svn://svn.zope.org/repos/main/zope.app.skins/tags/3.4.0/src/zope/app/skins sqlscript svn://svn.zope.org/repos/main/zope.app.sqlscript/tags/3.4.1/src/zope/app/sqlscript testing svn://svn.zope.org/repos/main/zope.app.testing/tags/3.4.1/src/zope/app/testing traversing svn://svn.zope.org/repos/main/zope.app.traversing/tags/3.4.0/src/zope/app/traversing tree svn://svn.zope.org/repos/main/zope.app.tree/tags/3.4.0/src/zope/app/tree undo
[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/app/ - Got publisher and publication backwards
Log message for revision 92594: - Got publisher and publication backwards Changed: _U Zope/trunk/lib/python/zope/app/ -=- Property changes on: Zope/trunk/lib/python/zope/app ___ Name: svn:externals - annotation svn://svn.zope.org/repos/main/zope.app.annotation/tags/3.4.0/src/zope/app/annotation apidoc svn://svn.zope.org/repos/main/zope.app.apidoc/tags/3.4.3/src/zope/app/apidoc applicationcontrol svn://svn.zope.org/repos/main/zope.app.applicationcontrol/tags/3.4.1/src/zope/app/applicationcontrol appsetup svn://svn.zope.org/repos/main/zope.app.appsetup/tags/3.4.1/src/zope/app/appsetup authentication svn://svn.zope.org/repos/main/zope.app.authentication/tags/3.4.1/src/zope/app/authentication basicskin svn://svn.zope.org/repos/main/zope.app.basicskin/tags/3.4.0/src/zope/app/basicskin broken svn://svn.zope.org/repos/main/zope.app.broken/tags/3.4.0/src/zope/app/broken cache svn://svn.zope.org/repos/main/zope.app.cache/tags/3.4.0/src/zope/app/cache component svn://svn.zope.org/repos/main/zope.app.component/tags/3.5.0/src/zope/app/component container svn://svn.zope.org/repos/main/zope.app.container/tags/3.6.2/src/zope/app/container content svn://svn.zope.org/repos/main/zope.app.content/tags/3.4.0/src/zope/app/content debug svn://svn.zope.org/repos/main/zope.app.debug/tags/3.4.0/src/zope/app/debug dependable svn://svn.zope.org/repos/main/zope.app.dependable/tags/3.4.0/src/zope/app/dependable error svn://svn.zope.org/repos/main/zope.app.error/tags/3.5.1/src/zope/app/error exception svn://svn.zope.org/repos/main/zope.app.exception/tags/3.4.1/src/zope/app/exception file svn://svn.zope.org/repos/main/zope.app.file/tags/3.4.2/src/zope/app/file folder svn://svn.zope.org/repos/main/zope.app.folder/tags/3.4.0/src/zope/app/folder form svn://svn.zope.org/repos/main/zope.app.form/tags/3.6.3/src/zope/app/form generations svn://svn.zope.org/repos/main/zope.app.generations/tags/3.4.1/src/zope/app/generations http svn://svn.zope.org/repos/main/zope.app.http/tags/3.4.1/src/zope/app/http i18n svn://svn.zope.org/repos/main/zope.app.i18n/tags/3.4.4/src/zope/app/i18n interface svn://svn.zope.org/repos/main/zope.app.interface/tags/3.4.0/src/zope/app/interface intid svn://svn.zope.org/repos/main/zope.app.intid/tags/3.4.1/src/zope/app/intid keyreference svn://svn.zope.org/repos/main/zope.app.keyreference/tags/3.4.1/src/zope/app/keyreference layers svn://svn.zope.org/repos/main/zope.app.layers/tags/3.4.0/src/zope/app/layers locales svn://svn.zope.org/repos/main/zope.app.locales/tags/3.4.1/src/zope/app/locales onlinehelp svn://svn.zope.org/repos/main/zope.app.onlinehelp/tags/3.4.1/src/zope/app/onlinehelp pagetemplate svn://svn.zope.org/repos/main/zope.app.pagetemplate/tags/3.4.0/src/zope/app/pagetemplate pluggableauth svn://svn.zope.org/repos/main/zope.app.pluggableauth/tags/3.4.0/src/zope/app/pluggableauth preference svn://svn.zope.org/repos/main/zope.app.preference/tags/3.4.1/src/zope/app/preference preview svn://svn.zope.org/repos/main/zope.app.preview/tags/3.4.0/src/zope/app/preview principalannotation svn://svn.zope.org/repos/main/zope.app.principalannotation/tags/3.4.0/src/zope/app/principalannotation publication svn://svn.zope.org/repos/main/zope.app.publication/tags/3.5.1/src/zope/app/publication publisher svn://svn.zope.org/repos/main/zope.app.publisher/trunk/src/zope/app/publisher renderer svn://svn.zope.org/repos/main/zope.app.renderer/tags/3.4.0/src/zope/app/renderer rotterdam svn://svn.zope.org/repos/main/zope.app.rotterdam/tags/3.4.1/src/zope/app/rotterdam schema svn://svn.zope.org/repos/main/zope.app.schema/tags/3.4.0/src/zope/app/schema security svn://svn.zope.org/repos/main/zope.app.security/tags/3.5.2/src/zope/app/security securitypolicy svn://svn.zope.org/repos/main/zope.app.securitypolicy/tags/3.4.6/src/zope/app/securitypolicy session svn://svn.zope.org/repos/main/zope.app.session/tags/3.5.1/src/zope/app/session skins svn://svn.zope.org/repos/main/zope.app.skins/tags/3.4.0/src/zope/app/skins sqlscript svn://svn.zope.org/repos/main/zope.app.sqlscript/tags/3.4.1/src/zope/app/sqlscript testing svn://svn.zope.org/repos/main/zope.app.testing/tags/3.5.6/src/zope/app/testing traversing svn://svn.zope.org/repos/main/zope.app.traversing/tags/3.4.0/src/zope/app/traversing tree svn://svn.zope.org/repos/main/zope.app.tree/tags/3.4.0/src/zope/app/tree undo
[Zope-Checkins] SVN: Zope/trunk/lib/python/Products/PythonScripts/patches.py - Since it's fixed after 2.4.5, no reason to apply the patch otherwise
Log message for revision 92595: - Since it's fixed after 2.4.5, no reason to apply the patch otherwise Changed: U Zope/trunk/lib/python/Products/PythonScripts/patches.py -=- Modified: Zope/trunk/lib/python/Products/PythonScripts/patches.py === --- Zope/trunk/lib/python/Products/PythonScripts/patches.py 2008-10-26 14:31:48 UTC (rev 92594) +++ Zope/trunk/lib/python/Products/PythonScripts/patches.py 2008-10-26 15:02:32 UTC (rev 92595) @@ -13,6 +13,8 @@ # Written by Marc-Andre Lemburg ([EMAIL PROTECTED]). # (c) Copyright CNRI, All Rights Reserved. NO WARRANTY. +import sys + def search_function(encoding): # Cache lookup @@ -93,7 +95,7 @@ # Return the registry entry return entry +if sys.version_info = (2, 4, 5): +import encodings +encodings.search_function.func_code = search_function.func_code -import encodings -encodings.search_function.func_code = search_function.func_code - ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/Products/ZCatalog/Catalog.py removed unused local variable
Log message for revision 92596: removed unused local variable Changed: U Zope/trunk/lib/python/Products/ZCatalog/Catalog.py -=- Modified: Zope/trunk/lib/python/Products/ZCatalog/Catalog.py === --- Zope/trunk/lib/python/Products/ZCatalog/Catalog.py 2008-10-26 15:02:32 UTC (rev 92595) +++ Zope/trunk/lib/python/Products/ZCatalog/Catalog.py 2008-10-26 15:08:37 UTC (rev 92596) @@ -332,7 +332,6 @@ if idxs is None: idxs = [] -data = self.data index = self.uids.get(uid, None) if index is None: # we are inserting new data ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/ - Revert to an older zope.testing. New one is way too new
Log message for revision 92597: - Revert to an older zope.testing. New one is way too new Changed: _U Zope/trunk/lib/python/zope/ -=- Property changes on: Zope/trunk/lib/python/zope ___ Name: svn:externals - annotation svn://svn.zope.org/repos/main/zope.annotation/tags/3.4.0/src/zope/annotation cachedescriptors svn://svn.zope.org/repos/main/zope.cachedescriptors/tags/3.4.0/src/zope/cachedescriptors component svn://svn.zope.org/repos/main/zope.component/tags/3.4.0/src/zope/component configuration svn://svn.zope.org/repos/main/zope.configuration/tags/3.4.0/src/zope/configuration contentprovider svn://svn.zope.org/repos/main/zope.contentprovider/tags/3.4.0/src/zope/contentprovider contenttype svn://svn.zope.org/repos/main/zope.contenttype/tags/3.4.0/src/zope/contenttype copypastemove svn://svn.zope.org/repos/main/zope.copypastemove/tags/3.4.0/src/zope/copypastemove datetime svn://svn.zope.org/repos/main/zope.datetime/tags/3.4.0/src/zope/datetime decorator svn://svn.zope.org/repos/main/zope.decorator/tags/3.4.0/src/zope/decorator deferredimport svn://svn.zope.org/repos/main/zope.deferredimport/tags/3.4.0/src/zope/deferredimport deprecation svn://svn.zope.org/repos/main/zope.deprecation/tags/3.4.0/src/zope/deprecation documenttemplate svn://svn.zope.org/repos/main/zope.documenttemplate/tags/3.4.2/src/zope/documenttemplate dottedname svn://svn.zope.org/repos/main/zope.dottedname/tags/3.4.2/src/zope/dottedname dublincore svn://svn.zope.org/repos/main/zope.dublincore/tags/3.4.0/src/zope/dublincore error svn://svn.zope.org/repos/main/zope.error/tags/3.5.1/src/zope/error event svn://svn.zope.org/repos/main/zope.event/tags/3.4.0/src/zope/event exceptions svn://svn.zope.org/repos/main/zope.exceptions/tags/3.4.0/src/zope/exceptions filerepresentation svn://svn.zope.org/repos/main/zope.filerepresentation/tags/3.4.0/src/zope/filerepresentation formlib svn://svn.zope.org/repos/main/zope.formlib/tags/3.4.0/src/zope/formlib hookable svn://svn.zope.org/repos/main/zope.hookable/tags/3.4.0/src/zope/hookable i18nmessageid svn://svn.zope.org/repos/main/zope.i18nmessageid/tags/3.4.3/src/zope/i18nmessageid i18n svn://svn.zope.org/repos/main/zope.i18n/tags/3.4.0/src/zope/i18n index svn://svn.zope.org/repos/main/zope.index/tags/3.4.1/src/zope/index interface svn://svn.zope.org/repos/main/zope.interface/tags/3.4.1/src/zope/interface lifecycleevent svn://svn.zope.org/repos/main/zope.lifecycleevent/tags/3.4.0/src/zope/lifecycleevent location svn://svn.zope.org/repos/main/zope.location/tags/3.4.0/src/zope/location minmax svn://svn.zope.org/repos/main/zope.minmax/tags/1.1.0/src/zope/minmax modulealias svn://svn.zope.org/repos/main/zope.modulealias/tags/3.4.0/src/zope/modulealias pagetemplate svn://svn.zope.org/repos/main/zope.pagetemplate/tags/3.4.0/src/zope/pagetemplate proxy svn://svn.zope.org/repos/main/zope.proxy/tags/3.4.0/src/zope/proxy publisher svn://svn.zope.org/repos/main/zope.publisher/tags/3.4.3/src/zope/publisher rdb svn://svn.zope.org/repos/main/zope.rdb/tags/3.4.0/src/zope/rdb schema svn://svn.zope.org/repos/main/zope.schema/tags/3.4.0/src/zope/schema security svn://svn.zope.org/repos/main/zope.security/tags/3.4.0/src/zope/security sequencesort svn://svn.zope.org/repos/main/zope.sequencesort/tags/3.4.0/src/zope/sequencesort sendmail svn://svn.zope.org/repos/main/zope.sendmail/tags/3.5.0/src/zope/sendmail server svn://svn.zope.org/repos/main/zope.server/tags/3.4.1/src/zope/server session svn://svn.zope.org/repos/main/zope.session/tags/3.4.1/src/zope/session size svn://svn.zope.org/repos/main/zope.size/tags/3.4.0/src/zope/size securitypolicy svn://svn.zope.org/repos/main/zope.securitypolicy/tags/3.4.0/src/zope/securitypolicy structuredtext svn://svn.zope.org/repos/main/zope.structuredtext/tags/3.4.0/src/zope/structuredtext tales svn://svn.zope.org/repos/main/zope.tales/tags/3.4.0/src/zope/tales tal svn://svn.zope.org/repos/main/zope.tal/tags/3.4.1/src/zope/tal testbrowser svn://svn.zope.org/repos/main/zope.testbrowser/tags/3.4.2-zope2/src/zope/testbrowser testing svn://svn.zope.org/repos/main/zope.testing/tags/3.5.3/src/zope/testing thread svn://svn.zope.org/repos/main/zope.thread/tags/3.4/src/zope/thread traversing svn://svn.zope.org/repos/main/zope.traversing/tags/3.4.0/src/zope/traversing viewlet svn://svn.zope.org/repos/main/zope.viewlet/tags/3.4.2/src/zope/viewlet wfmc
[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/app/ - Newer zope.app.appsetup
Log message for revision 92598: - Newer zope.app.appsetup Changed: _U Zope/trunk/lib/python/zope/app/ -=- Property changes on: Zope/trunk/lib/python/zope/app ___ Name: svn:externals - annotation svn://svn.zope.org/repos/main/zope.app.annotation/tags/3.4.0/src/zope/app/annotation apidoc svn://svn.zope.org/repos/main/zope.app.apidoc/tags/3.4.3/src/zope/app/apidoc applicationcontrol svn://svn.zope.org/repos/main/zope.app.applicationcontrol/tags/3.4.1/src/zope/app/applicationcontrol appsetup svn://svn.zope.org/repos/main/zope.app.appsetup/tags/3.4.1/src/zope/app/appsetup authentication svn://svn.zope.org/repos/main/zope.app.authentication/tags/3.4.1/src/zope/app/authentication basicskin svn://svn.zope.org/repos/main/zope.app.basicskin/tags/3.4.0/src/zope/app/basicskin broken svn://svn.zope.org/repos/main/zope.app.broken/tags/3.4.0/src/zope/app/broken cache svn://svn.zope.org/repos/main/zope.app.cache/tags/3.4.0/src/zope/app/cache component svn://svn.zope.org/repos/main/zope.app.component/tags/3.5.0/src/zope/app/component container svn://svn.zope.org/repos/main/zope.app.container/tags/3.6.2/src/zope/app/container content svn://svn.zope.org/repos/main/zope.app.content/tags/3.4.0/src/zope/app/content debug svn://svn.zope.org/repos/main/zope.app.debug/tags/3.4.0/src/zope/app/debug dependable svn://svn.zope.org/repos/main/zope.app.dependable/tags/3.4.0/src/zope/app/dependable error svn://svn.zope.org/repos/main/zope.app.error/tags/3.5.1/src/zope/app/error exception svn://svn.zope.org/repos/main/zope.app.exception/tags/3.4.1/src/zope/app/exception file svn://svn.zope.org/repos/main/zope.app.file/tags/3.4.2/src/zope/app/file folder svn://svn.zope.org/repos/main/zope.app.folder/tags/3.4.0/src/zope/app/folder form svn://svn.zope.org/repos/main/zope.app.form/tags/3.6.3/src/zope/app/form generations svn://svn.zope.org/repos/main/zope.app.generations/tags/3.4.1/src/zope/app/generations http svn://svn.zope.org/repos/main/zope.app.http/tags/3.4.1/src/zope/app/http i18n svn://svn.zope.org/repos/main/zope.app.i18n/tags/3.4.4/src/zope/app/i18n interface svn://svn.zope.org/repos/main/zope.app.interface/tags/3.4.0/src/zope/app/interface intid svn://svn.zope.org/repos/main/zope.app.intid/tags/3.4.1/src/zope/app/intid keyreference svn://svn.zope.org/repos/main/zope.app.keyreference/tags/3.4.1/src/zope/app/keyreference layers svn://svn.zope.org/repos/main/zope.app.layers/tags/3.4.0/src/zope/app/layers locales svn://svn.zope.org/repos/main/zope.app.locales/tags/3.4.1/src/zope/app/locales onlinehelp svn://svn.zope.org/repos/main/zope.app.onlinehelp/tags/3.4.1/src/zope/app/onlinehelp pagetemplate svn://svn.zope.org/repos/main/zope.app.pagetemplate/tags/3.4.0/src/zope/app/pagetemplate pluggableauth svn://svn.zope.org/repos/main/zope.app.pluggableauth/tags/3.4.0/src/zope/app/pluggableauth preference svn://svn.zope.org/repos/main/zope.app.preference/tags/3.4.1/src/zope/app/preference preview svn://svn.zope.org/repos/main/zope.app.preview/tags/3.4.0/src/zope/app/preview principalannotation svn://svn.zope.org/repos/main/zope.app.principalannotation/tags/3.4.0/src/zope/app/principalannotation publication svn://svn.zope.org/repos/main/zope.app.publication/tags/3.5.0/src/zope/app/publication publisher svn://svn.zope.org/repos/main/zope.app.publisher/tags/3.5.1/src/zope/app/publisher renderer svn://svn.zope.org/repos/main/zope.app.renderer/tags/3.4.0/src/zope/app/renderer rotterdam svn://svn.zope.org/repos/main/zope.app.rotterdam/tags/3.4.1/src/zope/app/rotterdam schema svn://svn.zope.org/repos/main/zope.app.schema/tags/3.4.0/src/zope/app/schema security svn://svn.zope.org/repos/main/zope.app.security/tags/3.5.2/src/zope/app/security securitypolicy svn://svn.zope.org/repos/main/zope.app.securitypolicy/tags/3.4.6/src/zope/app/securitypolicy session svn://svn.zope.org/repos/main/zope.app.session/tags/3.5.1/src/zope/app/session skins svn://svn.zope.org/repos/main/zope.app.skins/tags/3.4.0/src/zope/app/skins sqlscript svn://svn.zope.org/repos/main/zope.app.sqlscript/tags/3.4.1/src/zope/app/sqlscript testing svn://svn.zope.org/repos/main/zope.app.testing/tags/3.5.6/src/zope/app/testing traversing svn://svn.zope.org/repos/main/zope.app.traversing/tags/3.4.0/src/zope/app/traversing tree svn://svn.zope.org/repos/main/zope.app.tree/tags/3.4.0/src/zope/app/tree undo
[Zope-Checkins] SVN: Zope/trunk/lib/python/ZServer/HTTPServer.py - Make it work with Python 2.4 too
Log message for revision 92607: - Make it work with Python 2.4 too Changed: U Zope/trunk/lib/python/ZServer/HTTPServer.py -=- Modified: Zope/trunk/lib/python/ZServer/HTTPServer.py === --- Zope/trunk/lib/python/ZServer/HTTPServer.py 2008-10-26 18:45:54 UTC (rev 92606) +++ Zope/trunk/lib/python/ZServer/HTTPServer.py 2008-10-26 20:41:03 UTC (rev 92607) @@ -45,9 +45,11 @@ from ZPublisher.HTTPRequest import HTTPRequest from App.config import getConfiguration +import asyncore +import asynchat + from medusa.http_server import http_server, get_header from medusa.http_server import fifo, http_channel, VERSION_STRING -import asyncore from medusa import counter, producers from medusa.test import max_sockets from medusa.default_handler import unquote @@ -335,7 +337,7 @@ def __init__(self, server, conn, addr): http_channel.__init__(self, server, conn, addr) -if isinstance(self.producer_fifo, fifo): +if isinstance(self.producer_fifo, (fifo, asynchat.fifo)): self.producer_fifo_push = self.producer_fifo.push self.producer_fifo_first = self.producer_fifo.first self.producer_fifo_pop = self.producer_fifo.pop @@ -348,7 +350,7 @@ del self.producer_fifo[0] self.producer_fifo_pop = pop requestCloseOnExec(conn) -self.queue=[] +self.queue = [] self.working=0 self.max_header_len = getConfiguration().http_header_max_length ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Zope Tests: 5 Failed
Summary of messages to the zope-tests list. Period Sat Oct 25 12:00:00 2008 UTC to Sun Oct 26 12:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures - Subject: FAILED (failures=1) : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Oct 25 20:59:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010366.html Subject: FAILED (failures=1) : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 25 21:00:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010367.html Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 25 21:02:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010368.html Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 25 21:03:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010369.html Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 25 21:05:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010370.html ___ 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] SVN: Zope/trunk/lib/python/zope/ - Revert to an older zope.testing. New one is way too new
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: Log message for revision 92597: - Revert to an older zope.testing. New one is way too new Before: testing svn://svn.zope.org/repos/main/zope.testing/tags/3.5.3/src/zope/testing After: testing svn://svn.zope.org/repos/main/zope.testing/tags/3.5.6/src/zope/testing Unless I'm seeing things, this is a bump to a newer version. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJBI4t+gerLs4ltQ4RAp5GAJwKox2PLxkNr7RNzq1BLFCWCH6cXACdEJJu GBp7u0bYrOsFTbcE+Fze1Gs= =qccz -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] Proposal: Make Zope2 smaller
Hi. I'd like to get feedback on an idea I had recently. Problem Zope2 currently includes large parts of Zope 3. Not all of the zope.* and zope.app.* packages are maintained or are in use. Still Zope 2 includes large amounts of them and thus implicitly advertises them to be used. In addition they blow up the installed code size and add a long term maintenance burden. The move to gain Python 2.6 compatibility has shown some of this and I expect to see more work in moving to Python 3 at a later stage. Assumption Zope 2.12 will most probably see two kind of distributions. One is a Zope2 egg, consisting of one large Zope2 egg which pulls in everything that has been eggified on their own as dependencies. This includes the ZODB and all zope.* and zope.app.* packages. The second distribution is a tradtional tarball, which exactly matches the current distribution format. Proposal I'd like to change the egg distribution alone and introduce one setuptools extra to it. The old tarball distribution would stay the same. The standard Zope2 egg install would only include those zope.* and zope.app.* packages which it actually requires. The extra would be called 'zope_app' and pull in all zope.* and zope.app.* packages which we did include so far, but are not actually required to run Zope 2. For example: extras_require = dict( zope_app = [ 'zope.app.rotterdam', 'zope.app', ], ), Rational Any package that does require any of the zope.* or zope.app.* packages can define those as an explicit dependency itself. The zope_app extra makes the transition phase easier, in which packages do not yet declare all their dependencies. In the long run, the extra can be dropped entirely. This proposal makes it possible to get a smaller, well-defined Zope2 egg. The first egg release of Zope2 gives us an opportunity to do this move without breaking backwards compatibility. While Zope 2 has included large parts of Zope 3, it never exactly included all of it. As Zope 3 is not likely to see an ongoing monolithic release, I don't see a reason for Zope 2 to include Zope 3 in the monolithic fashion we do so far. Implementation This is not yet implemented but should be quite easy. Figuring out the exact packages which are required by Zope 2 is to be done. Questions / Comments / Feedback Are more than welcome. 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] Proposal: Make Zope2 smaller
On 26.10.2008 16:37 Uhr, Hanno Schlichting wrote: Implementation This is not yet implemented but should be quite easy. Figuring out the exact packages which are required by Zope 2 is to be done. General +1 on getting rid of the dependencies which are actually no dependencies. However I have the feeling that there possibly only a small number of packages that are really have no dependency to Zope 2. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ 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] ZCatalog caching with memcached
On 26.10.2008 18:43 Uhr, Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. Path indexes and fulltext indexes have a much more complicated implementation compared to field or keyword indexes. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ 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] ZCatalog caching with memcached
Hi Roché, I can see your funkload profile? On Sun, Oct 26, 2008 at 3:43 PM, Roché Compaan [EMAIL PROTECTED]wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: Have you measures the time needs for some standard ZCatalog queries used with a Plone site with the communication overhead with memcached? Generally spoken: I think the ZCatalog is in general fast. Queries using a fulltext index are known to be more expensive or if you have to deal with large resultsets or complex queries. No I haven't. Roche Compaan has done extensive benchmarking using funkload testing plain catalog vs module level cache vs memcached, but the tests are more about page serving than catalog query time. I'll ask him to comment more on that. I actually did some profiling as well and catalog searches were just too damn slow. The average execution time for searchResults was 100 milliseconds and this is why I told Hedley we should do some caching at query level in the first place. I experimented with this idea a couple of years back but wasn't successful due to inexperience. I was trying to cache brains which obviously leads to persistency bugs. This time around it was obvious to me that we should cache the IISet result sets. I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. The effect on performance is really awesome, now we just need to fine tune the implementation. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ___ 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 ) -- Fábio Rizzo Matos ThreePointsWeb [EMAIL PROTECTED] http://www.threepointsweb.com +55 61 3202-6480 Python, Zope e Plone com quem entende do assunto! ___ 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] Proposal: Make Zope2 smaller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Hi. I'd like to get feedback on an idea I had recently. Problem Zope2 currently includes large parts of Zope 3. Not all of the zope.* and zope.app.* packages are maintained or are in use. Still Zope 2 includes large amounts of them and thus implicitly advertises them to be used. In addition they blow up the installed code size and add a long term maintenance burden. The move to gain Python 2.6 compatibility has shown some of this and I expect to see more work in moving to Python 3 at a later stage. Assumption Zope 2.12 will most probably see two kind of distributions. One is a Zope2 egg, consisting of one large Zope2 egg which pulls in everything that has been eggified on their own as dependencies. This includes the ZODB and all zope.* and zope.app.* packages. The second distribution is a tradtional tarball, which exactly matches the current distribution format. Proposal I'd like to change the egg distribution alone and introduce one setuptools extra to it. The old tarball distribution would stay the same. The standard Zope2 egg install would only include those zope.* and zope.app.* packages which it actually requires. The extra would be called 'zope_app' and pull in all zope.* and zope.app.* packages which we did include so far, but are not actually required to run Zope 2. For example: extras_require = dict( zope_app = [ 'zope.app.rotterdam', 'zope.app', ], ), Rational Any package that does require any of the zope.* or zope.app.* packages can define those as an explicit dependency itself. The zope_app extra makes the transition phase easier, in which packages do not yet declare all their dependencies. In the long run, the extra can be dropped entirely. This proposal makes it possible to get a smaller, well-defined Zope2 egg. The first egg release of Zope2 gives us an opportunity to do this move without breaking backwards compatibility. While Zope 2 has included large parts of Zope 3, it never exactly included all of it. As Zope 3 is not likely to see an ongoing monolithic release, I don't see a reason for Zope 2 to include Zope 3 in the monolithic fashion we do so far. Implementation This is not yet implemented but should be quite easy. Figuring out the exact packages which are required by Zope 2 is to be done. +1 to releasing a Zope 2.12 egg with minimal / correct dependencies. Perhaps the following script would help to identify them: http://www.tarind.com/py2depgraph.py Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJBK9s+gerLs4ltQ4RApXCAJ0XxxlGM6kqPiepsDySVXBA4C4NnQCeI53v qJcn001PPGZjJ1YlhUUMT0U= =UprJ -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] ZCatalog caching with memcached
Hi Fabio The funkload tests were project specific. I plan to write up my findings and to do benchmarks on a standard Plone instance and blog about it. This will unfortunately have to wait since I'm on holiday this week :-) -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za On Sun, 2008-10-26 at 15:54 -0200, Fabio Rizzo Matos wrote: Hi Roché, I can see your funkload profile? On Sun, Oct 26, 2008 at 3:43 PM, Roché Compaan [EMAIL PROTECTED] wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: Have you measures the time needs for some standard ZCatalog queries used with a Plone site with the communication overhead with memcached? Generally spoken: I think the ZCatalog is in general fast. Queries using a fulltext index are known to be more expensive or if you have to deal with large resultsets or complex queries. No I haven't. Roche Compaan has done extensive benchmarking using funkload testing plain catalog vs module level cache vs memcached, but the tests are more about page serving than catalog query time. I'll ask him to comment more on that. I actually did some profiling as well and catalog searches were just too damn slow. The average execution time for searchResults was 100 milliseconds and this is why I told Hedley we should do some caching at query level in the first place. I experimented with this idea a couple of years back but wasn't successful due to inexperience. I was trying to cache brains which obviously leads to persistency bugs. This time around it was obvious to me that we should cache the IISet result sets. I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. The effect on performance is really awesome, now we just need to fine tune the implementation. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ___ 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 ) -- Fábio Rizzo Matos ThreePointsWeb [EMAIL PROTECTED] http://www.threepointsweb.com +55 61 3202-6480 Python, Zope e Plone com quem entende do assunto! ___ 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 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] ZCatalog caching with memcached
On Sun, 2008-10-26 at 18:50 +0100, Andreas Jung wrote: On 26.10.2008 18:43 Uhr, Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. Path indexes and fulltext indexes have a much more complicated implementation compared to field or keyword indexes. I know, and this alone makes a good argument for caching at catalog level. In our case we used membrane, which makes an excessive amount of catalog queries when looking up users so some level of caching was essential. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ___ 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] ZCatalog caching with memcached
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: Have you measures the time needs for some standard ZCatalog queries used with a Plone site with the communication overhead with memcached? Generally spoken: I think the ZCatalog is in general fast. Queries using a fulltext index are known to be more expensive or if you have to deal with large resultsets or complex queries. No I haven't. Roche Compaan has done extensive benchmarking using funkload testing plain catalog vs module level cache vs memcached, but the tests are more about page serving than catalog query time. I'll ask him to comment more on that. I actually did some profiling as well and catalog searches were just too damn slow. The average execution time for searchResults was 100 milliseconds and this is why I told Hedley we should do some caching at query level in the first place. I experimented with this idea a couple of years back but wasn't successful due to inexperience. I was trying to cache brains which obviously leads to persistency bugs. This time around it was obvious to me that we should cache the IISet result sets. I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. The effect on performance is really awesome, now we just need to fine tune the implementation. Before (or while) we work on caching, can we try to improve the underlying indexes, and the way that applications use them? I'm pretty sure that there is a lot of room for improvement: - Plone uses too many indexes, and in particular, uses multiple text indexes. Having extra indexes around just in case is a sure lose a write time, and may even be expensive at query time (depending on the query). - Particular indexes have performance characteristics based on their designed purpose: for instance, the stock FieldIndex implementation assumes that the number of documents indexed will be the number of discrete indexable values. Using such an index in an application domain with a very large set of indexable values probably loses, and in ways which don't show up in early / small-scale testing. - I'm pretty sure that we haven't yet found the best data structure for hierarchy indexes (e.g., the Plone EPI index, or the stock Zope2 PathIndex, etc.). Something like a 'trie' might be optimal for pure prefix searching of hierarchies. - I am confident that the TopicIndex is underutiliized: it does *all* the work for a given query at write time, and can thus be blindingly fast at query time. - Other special-purpose indexes (e.g., a recent items index) would be worth a look, especially for applications with large volumes of content. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJBLHb+gerLs4ltQ4RAp59AJwNlfjI0tBv4PdMiDdH4TLKSm5YfwCgu8xB F3u1G0onXKKZ4s7MbLj9B2w= =r0oE -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] ZCatalog caching with memcached
Very Nice. Have a nice holiday :-) On Sun, Oct 26, 2008 at 3:58 PM, Roché Compaan [EMAIL PROTECTED]wrote: Hi Fabio The funkload tests were project specific. I plan to write up my findings and to do benchmarks on a standard Plone instance and blog about it. This will unfortunately have to wait since I'm on holiday this week :-) -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za On Sun, 2008-10-26 at 15:54 -0200, Fabio Rizzo Matos wrote: Hi Roché, I can see your funkload profile? On Sun, Oct 26, 2008 at 3:43 PM, Roché Compaan [EMAIL PROTECTED] wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: Have you measures the time needs for some standard ZCatalog queries used with a Plone site with the communication overhead with memcached? Generally spoken: I think the ZCatalog is in general fast. Queries using a fulltext index are known to be more expensive or if you have to deal with large resultsets or complex queries. No I haven't. Roche Compaan has done extensive benchmarking using funkload testing plain catalog vs module level cache vs memcached, but the tests are more about page serving than catalog query time. I'll ask him to comment more on that. I actually did some profiling as well and catalog searches were just too damn slow. The average execution time for searchResults was 100 milliseconds and this is why I told Hedley we should do some caching at query level in the first place. I experimented with this idea a couple of years back but wasn't successful due to inexperience. I was trying to cache brains which obviously leads to persistency bugs. This time around it was obvious to me that we should cache the IISet result sets. I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. The effect on performance is really awesome, now we just need to fine tune the implementation. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ___ 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 ) -- Fábio Rizzo Matos ThreePointsWeb [EMAIL PROTECTED] http://www.threepointsweb.com +55 61 3202-6480 Python, Zope e Plone com quem entende do assunto! ___ 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 ) -- Fábio Rizzo Matos ThreePointsWeb [EMAIL PROTECTED] http://www.threepointsweb.com +55 61 3202-6480 Python, Zope e Plone com quem entende do assunto! ___ 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] New zope.interface release
Hi, I just released a new zope.interface 3.5.0 to be found at http://pypi.python.org/pypi/zope.interface I uploaded a zipped source distribution and (as we have C extensions) Windows installers for Python 2.4, 2.5 and 2.6. Please contact me, if you find problems with 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 )
Re: [Zope-dev] ZCatalog caching with memcached
On 26.10.2008 19:05 Uhr, Roché Compaan wrote: On Sun, 2008-10-26 at 18:50 +0100, Andreas Jung wrote: On 26.10.2008 18:43 Uhr, Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. Path indexes and fulltext indexes have a much more complicated implementation compared to field or keyword indexes. I know, and this alone makes a good argument for caching at catalog level. In our case we used membrane, which makes an excessive amount of catalog queries when looking up users so some level of caching was essential. First caching is good thing :-) But how about the following issue: CMF/Plone inject additional subqueries for expires/effective/typesAndRoles. At least the security related aubqueries make a cached catalog result very specific to a particular user. That seems to be very ok for a site with lots of anonymous users - it might be an issue with lots of authenticated users. It might be necessary to add some kind of intelligence to decide what to cache and what not. I don't think it does not make sense to cache the result of a fulltext search. I am just thinking if it would make sense to cache on the index level instead of catalog level? So you could for example cache expensive index queries (path index) and combine them with uncached index which are supposed to be fast..however such decisions require detailed mesurements on real systems. One other thing concerning memcached: there is obviously a limit to 1MB for data you can store as a value. We have not found an obvious way for increasing this limit other by patching the memcached sources. We came up with an implementation where data 1MB is split up into individual junks (we have a dedicated set_huge(), get_huge()) implementation. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - 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:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ 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] New zope.interface release
Hanno Schlichting wrote: I just released a new zope.interface 3.5.0 to be found at http://pypi.python.org/pypi/zope.interface I uploaded a zipped source distribution and (as we have C extensions) Windows installers for Python 2.4, 2.5 and 2.6. Spotting my own mistake, I uploaded binary eggs for all three Python versions for Windows now. I left the installers in place. 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] Proposal: Make Zope2 smaller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 26, 2008, at 16:37 , Hanno Schlichting wrote: I'd like to change the egg distribution alone and introduce one setuptools extra to it. The old tarball distribution would stay the same. The standard Zope2 egg install would only include those zope.* and zope.app.* packages which it actually requires. +1 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkkE0w0ACgkQRAx5nvEhZLLYtACgh7Z7kcNqwlpV8nrAZDYOjeAr aswAniNTbZeVm2me0RTRxTZVct27YsQQ =5j9f -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] Convertion to named character entities
On 26.10.2008 15:10 Uhr, Jakob Schou Jensen wrote: Is there any way to convert special characters in a string to named character entities? The string is obtained from a form field. Look at the htmlentitydefs module of Python. -aj begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Iowa Python User's Group Meeting (November 3rd)
Hi, The next Iowa Python Users Group (AKA Pyowa) is nearly upon us. We will be meeting November 3rd, from 7-9 p.m. at the following location: Marshall County Sheriff's Office 2369 Jessup Ave Marshalltown, IA 50158 At this meeting, we will be having a Crash Course of sorts for all the new programmers in our group. As anyone who has ever taken a programming course know, it is impossible to teach everything in two hours, so we'll be focusing on tools that will allow our group to help themselves. In other words, we'll be focusing on source code analysis techniques like introspection and how to use IDLE effectively. There will also be a presentation on basic GUI design and also Django. We will have 8 laptops there to use for any new people, pre-loaded with Python 2.5.2 and any additional packages we need for our presentations. You are welcome to bring your own laptop if you want. Be sure to have 2.5 on yours as well as wxPython and the PyWin32 package (if you use Windows). We will have them on USB flash drives should you forget. Free pop and bottled water will be provided. Questions and comments can be directed to mike [at] pythonlibrary [dot] org. Updates can be found at http://www.ipug.pythonlibrary.org --- Mike Driscoll Blog: http://blog.pythonlibrary.org Python Extension Building Network: http://www.pythonlibrary.org ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
