Re: [Zope-CMF] cmf-tests - OK: 2, UNKNOWN: 6
On 12/8/12 5:00 PM, CMF tests summarizer wrote: This is the summary for test reports received on the cmf-tests list between 2012-12-07 00:00:00 UTC and 2012-12-08 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received CMF-2.2 Zope-2.12 Python-2.6.8 : Linux CMF-2.2 Zope-2.13 Python-2.6.8 : Linux [1]FAILED (failures=1) : CMF-2.3 Zope-2.13 Python-2.6.8 : Linux [2]FAILED (failures=1) : CMF-2.3 Zope-trunk Python-2.6.8 : Linux [3]FAILED (failures=1) : CMF-trunk Zope-2.13 Python-2.6.8 : Linux [4]FAILED (failures=1) : CMF-trunk Zope-2.13 Python-2.7.3 : Linux [5]FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.8 : Linux [6]FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.7.3 : Linux Non-OK results -- [1]UNKNOWN FAILED (failures=1) : CMF-2.3 Zope-2.13 Python-2.6.8 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017412.html [2]UNKNOWN FAILED (failures=1) : CMF-2.3 Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017413.html [3]UNKNOWN FAILED (failures=1) : CMF-trunk Zope-2.13 Python-2.6.8 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017414.html [4]UNKNOWN FAILED (failures=1) : CMF-trunk Zope-2.13 Python-2.7.3 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017415.html [5]UNKNOWN FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017416.html [6]UNKNOWN FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/cmf-tests/2012-December/017417.html These are my fault; I reverted the change that caused them. ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] [Checkins] SVN: z3c.form/trunk/setup.py Get ready for 2.6.1 release.
On 2/16/12 11:55 PM, Adam GROSZER wrote: Hello, So you say that if I add ... entry_points={ 'zest.releaser.releaser.after_checkout': [ 'zest_pocompile = zest.pocompile.compile:compile_in_tag', ], }, ... to z3c.form's setup.py fullrelease will take care of the po files? You'll have to experiment -- the suggestion was based on what I've heard, not personal experience with zest.releaser. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.tal release
I made a fix [1] in zope.tal so that it won't raise NestingErrors while parsing script tags that contain markup as part of the script. Could someone make a new release or give me (davisagli on PyPI) access to? thanks, David [1] http://zope3.pov.lt/trac/changeset/124396 -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [zope2] 2.12.x formal end-of-life
On Feb 6, 2012, at 9:45 AM, Hanno Schlichting wrote: Hi. I just updated the 2.12.x branch with one last batch of bugfix versions. I'll let the buildbots run and if there's no troubles release one more version later this week. I consider this to be the last maintenance release for the 2.12.x series. From now on 2.12.x will only see security updates. I've also put an end-date to the security support (http://zope2.zope.org/releases), stating October 2013 as the end date. This happens to be the end of security support for Python 2.6 - the only Python version supported by the 2.12.x series. This is rather long in the future, one and a half years from now. I think that sets reasonable expectations and gives us a clear end date. It's not meant to prohibit anyone from doing security releases after this date - just set clear expectations to others, like Linux distributors shipping Zope 2 and relieve me of my formal duty ;-) The 2.13 series is going to be supported longer. How long depends on Python 2.7's support and how Zope 4 is going to progress. At this point there's no formal end-of-life date. If you have concerns, please speak up. Zope 2.x release managerly yours ;-) Hanno Sounds good to me. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: z3c.form/trunk/setup.py Get ready for 2.6.1 release.
On 1/30/12 11:15 PM, Adam GROSZER wrote: Hello, I think we need to automate sdist upload, the .mo files are missing from the release. Any ideas other than patching setup.py to create the .mo files automatically? See zest.releaser [1] and its plugin zest.pocompile [2] [1] http://pypi.python.org/pypi/zest.releaser [2] http://pypi.python.org/pypi/zest.pocompile David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Engagement technology for social and environmental change. http://www.groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On 12/15/11 9:15 AM, Jim Fulton wrote: I'm going to take the liberty of creating a new package in the zope.app namespace. It's a small package that allows, zope.app-based applications to be wired up to WSGI middleware and servers using the paste-deploy framework. (Hopefully, I didn't miss something that already does this. I'm not sure where I would look for such a thing.) If anyone objects (or if this is duplicating something that already exists), please let me know. There is http://pypi.python.org/pypi/zope.app.wsgi David -- David Glick Web Developer davidgl...@groundwireconsulting.com 206.286.1235x32 Groundwire Consulting is here. http://groundwire.org/about/FAQ-gw-consulting ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/branches/davisagli-copy-export/ branch for work on making copy export not follow parent pointers
Log message for revision 123213: branch for work on making copy export not follow parent pointers Changed: A Zope/branches/davisagli-copy-export/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/elro-parent-pointers/s copy objects using zope.copy (test failing until elro checks in his changes)
Log message for revision 123221: copy objects using zope.copy (test failing until elro checks in his changes) Changed: U Zope/branches/elro-parent-pointers/setup.py U Zope/branches/elro-parent-pointers/src/OFS/CopySupport.py U Zope/branches/elro-parent-pointers/src/OFS/configure.zcml U Zope/branches/elro-parent-pointers/src/OFS/tests/testCopySupport.py -=- Modified: Zope/branches/elro-parent-pointers/setup.py === --- Zope/branches/elro-parent-pointers/setup.py 2011-10-31 22:44:53 UTC (rev 123220) +++ Zope/branches/elro-parent-pointers/setup.py 2011-10-31 23:08:40 UTC (rev 123221) @@ -79,6 +79,7 @@ 'zope.container', 'zope.contentprovider', 'zope.contenttype', + 'zope.copy', 'zope.deferredimport', 'zope.event', 'zope.exceptions', Modified: Zope/branches/elro-parent-pointers/src/OFS/CopySupport.py === --- Zope/branches/elro-parent-pointers/src/OFS/CopySupport.py 2011-10-31 22:44:53 UTC (rev 123220) +++ Zope/branches/elro-parent-pointers/src/OFS/CopySupport.py 2011-10-31 23:08:40 UTC (rev 123221) @@ -18,7 +18,6 @@ from marshal import loads import re import sys -import tempfile from urllib import quote from urllib import unquote import warnings @@ -47,6 +46,7 @@ from zope.lifecycleevent import ObjectCopiedEvent from zope.lifecycleevent import ObjectMovedEvent from zope.container.contained import notifyContainerModified +from zope.copy import copy from OFS.event import ObjectWillBeMovedEvent from OFS.event import ObjectClonedEvent @@ -582,11 +582,7 @@ `container`) # Ask an object for a new copy of itself. -f=tempfile.TemporaryFile() -self._p_jar.exportFile(self._p_oid,f) -f.seek(0) -ob=container._p_jar.importFile(f) -f.close() +ob = copy(aq_base(self)) return ob def _postCopy(self, container, op=0): Modified: Zope/branches/elro-parent-pointers/src/OFS/configure.zcml === --- Zope/branches/elro-parent-pointers/src/OFS/configure.zcml 2011-10-31 22:44:53 UTC (rev 123220) +++ Zope/branches/elro-parent-pointers/src/OFS/configure.zcml 2011-10-31 23:08:40 UTC (rev 123221) @@ -4,4 +4,6 @@ include file=deprecated.zcml/ include file=event.zcml/ + adapter factory=zope.location.pickling.LocationCopyHook / + /configure Modified: Zope/branches/elro-parent-pointers/src/OFS/tests/testCopySupport.py === --- Zope/branches/elro-parent-pointers/src/OFS/tests/testCopySupport.py 2011-10-31 22:44:53 UTC (rev 123220) +++ Zope/branches/elro-parent-pointers/src/OFS/tests/testCopySupport.py 2011-10-31 23:08:40 UTC (rev 123221) @@ -12,6 +12,10 @@ from OFS.Folder import manage_addFolder from OFS.Image import manage_addFile from Testing.makerequest import makerequest +from zope import component +from zope.testing import cleanup +from persistent import Persistent +from zope.location import Location ADD_IMAGES_AND_FILES = 'Add images and files' @@ -62,6 +66,11 @@ s = DemoStorage() return ZODB.DB( s ).open() + +class PersistentLocation(Persistent, Location): +pass + + class CopySupportTestBase(unittest.TestCase): def _initFolders(self): @@ -102,10 +111,16 @@ del self.responseOut del self.root del self.connection +cleanup.cleanUp() + class TestCopySupport( CopySupportTestBase ): def setUp( self ): +from zope.copy.interfaces import ICopyHook +from zope.location.interfaces import ILocation +from zope.location.pickling import LocationCopyHook +component.provideAdapter(LocationCopyHook, (ILocation,), ICopyHook) folder1, folder2 = self._initFolders() @@ -152,6 +167,7 @@ self.folder2.manage_pasteObjects( cookie ) self.assertTrue( 'file' in self.folder1.objectIds() ) self.assertTrue( 'file' in self.folder2.objectIds() ) +self.assertTrue(self.folder2.file.__parent__ is self.folder2) def testCut( self ): self.assertTrue( 'file' in self.folder1.objectIds() ) @@ -169,7 +185,16 @@ self.folder2.manage_pasteObjects(cookie) self.assertTrue('newfile' in self.folder1.objectIds()) self.assertTrue('newfile' in self.folder2.objectIds()) + +def testCopyExcludesNoncontainedObjects(self): +self.app.other_ob = other_ob = PersistentLocation() +self.app.other_ob.__parent__ = self.app +ob = self.folder1.file +ob.other_ob = self.app.other_ob +copied_ob = ob._getCopy(self.folder1) +self.assertTrue(copied_ob.other_ob is other_ob) + def testPasteSingleNotSameID( self ): self.assertTrue( 'file' in self.folder1.objectIds() ) self.assertFalse( 'file' in
[Zope-Checkins] SVN: Zope/branches/davisagli-copy-export/ remove unused branch
Log message for revision 123222: remove unused branch Changed: D Zope/branches/davisagli-copy-export/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] Zope 4?
On 10/27/11 9:05 AM, Jim Fulton wrote: I saw Zope 4 mentioned in public today. This is the first time I'd seen it mentioned in public. Is there a more formal announcement anywhere? Is there a description of what it is envisioned to be? That came out of this thread on zope-dev back in July: https://mail.zope.org/pipermail/zope-dev/2011-July/043158.html David -- David Glick Web Developer davidgl...@groundwireconsulting.com 206.286.1235x32 Groundwire Consulting is here. http://groundwire.org/about/FAQ-gw-consulting ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Sharing session between different zope servers
On 6/15/11 10:01 AM, Martin Aspeli wrote: Hi, You can use collective.beaker to manage your sessions with beaker, and store on the filesystem (if all on the same server) or memcached (if on different servers). That's a code change, though. Products.BeakerSessionDataManager uses collective.beaker as a backend for standard Zope sessions so you don't have to change code. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 GiveBIG is coming! Give to Groundwire on June 23 and The Seattle Foundation will stretch your money! http://www.groundwire.org/blog/give-big-is-coming ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Blob detection in the ZODB for bug 739692
On 4/26/11 7:40 AM, William Heymann wrote: I am working on a patch for Blob support in OFS.Image/File and I am running into a small problem. What is the correct way to detect if the current ZODB supports blobs? If I just do self.data = ZODB.blob.Blob(data) in update_data in OFS.Image and a system does not support blobs I get this error Traceback (innermost last): Module ZPublisher.Publish, line 134, in publish Module Zope2.App.startup, line 301, in commit Module transaction._manager, line 89, in commit Module transaction._transaction, line 329, in commit Module transaction._transaction, line 443, in _commitResources Module ZODB.Connection, line 563, in commit Module ZODB.Connection, line 619, in _commit Module ZODB.Connection, line 662, in _store_objects Unsupported: Storing Blobs inZEO.ClientStorage.ClientStorage object at 0x3248590 is not supported. which does not even mention OFS.Image anywhere I tried putting in try: self.data = ZODB.blob.Blob(data) except zExceptions.Unsupported: self.data = data and this of course did not work since the error is not actually occurring here. What I am trying to do is make is to that Blobs are used if blobs are supported and not used if they are not currently supported. For all of my systems this is not an issue since I only support blobs but for a patch to be accepeted it seems that it would need to work either way. I considered putting in a configuration switch in zope.conf to say if blobs should be used or not so that it is up to the developer to set the switch and enable blob support and the system would just give errors if setup incorrectly but that does not seem like a good idea. You can get (persistent object)._p_jar.db().storage and check if it provides ZODB.interfaces.IBlobStorage. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] proposed ZNagios changes
I'd like to make a couple changes to Products.ZNagios: 1. Add an optional setting in the munin plugin configuration to control which database to report metrics for, in Zope instances with multiple mountpoints. 2. Make the cacheconnections graph not assume that there are 4 connections. Are these changes okay? And can someone add me to the package on pypi (uid: davisagli)? thanks, David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/branches/davisagli-exclude-parent-pointers-from-export/ branch for excluding parent pointers from ZEXP export
Log message for revision 120864: branch for excluding parent pointers from ZEXP export Changed: A Zope/branches/davisagli-exclude-parent-pointers-from-export/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/OFS/ObjectManager.py remove parent pointer while exporting
Log message for revision 120865: remove parent pointer while exporting Changed: U Zope/trunk/src/OFS/ObjectManager.py -=- Modified: Zope/trunk/src/OFS/ObjectManager.py === --- Zope/trunk/src/OFS/ObjectManager.py 2011-03-11 14:48:34 UTC (rev 120864) +++ Zope/trunk/src/OFS/ObjectManager.py 2011-03-11 14:53:59 UTC (rev 120865) @@ -22,6 +22,7 @@ import os import re import sys +import transaction from AccessControl import ClassSecurityInfo from AccessControl.class_init import InitializeClass @@ -584,11 +585,25 @@ cfg = getConfiguration() f = os.path.join(cfg.clienthome, '%s.%s' % (id, suffix)) -if toxml: -exportXML(ob._p_jar, ob._p_oid, f) -else: -ob._p_jar.exportFile(ob._p_oid, f) +ob = aq_base(ob) +parent = getattr(ob, '__parent__', _marker) +if parent is not _marker: +sp = transaction.savepoint(True) +del ob.__parent__ +# create a savepoint so that the export includes the version +# without a __parent__ pointer +transaction.savepoint(True) +try: +if toxml: +exportXML(ob._p_jar, ob._p_oid, f) +else: +ob._p_jar.exportFile(ob._p_oid, f) +finally: +if parent is not _marker: +# roll back so that we don't actually remove the __parent__ +sp.rollback() + if REQUEST is not None: return self.manage_main(self, REQUEST, manage_tabs_message= ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/OFS/ObjectManager.py revert accidental commit
Log message for revision 120866: revert accidental commit Changed: U Zope/trunk/src/OFS/ObjectManager.py -=- Modified: Zope/trunk/src/OFS/ObjectManager.py === --- Zope/trunk/src/OFS/ObjectManager.py 2011-03-11 14:53:59 UTC (rev 120865) +++ Zope/trunk/src/OFS/ObjectManager.py 2011-03-11 14:54:33 UTC (rev 120866) @@ -22,7 +22,6 @@ import os import re import sys -import transaction from AccessControl import ClassSecurityInfo from AccessControl.class_init import InitializeClass @@ -585,25 +584,11 @@ cfg = getConfiguration() f = os.path.join(cfg.clienthome, '%s.%s' % (id, suffix)) +if toxml: +exportXML(ob._p_jar, ob._p_oid, f) +else: +ob._p_jar.exportFile(ob._p_oid, f) -ob = aq_base(ob) -parent = getattr(ob, '__parent__', _marker) -if parent is not _marker: -sp = transaction.savepoint(True) -del ob.__parent__ -# create a savepoint so that the export includes the version -# without a __parent__ pointer -transaction.savepoint(True) -try: -if toxml: -exportXML(ob._p_jar, ob._p_oid, f) -else: -ob._p_jar.exportFile(ob._p_oid, f) -finally: -if parent is not _marker: -# roll back so that we don't actually remove the __parent__ -sp.rollback() - if REQUEST is not None: return self.manage_main(self, REQUEST, manage_tabs_message= ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py remove parent pointer while exporting
Log message for revision 120867: remove parent pointer while exporting Changed: U Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py -=- Modified: Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py === --- Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py 2011-03-11 14:54:33 UTC (rev 120866) +++ Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py 2011-03-11 14:55:44 UTC (rev 120867) @@ -22,6 +22,7 @@ import os import re import sys +import transaction from AccessControl import ClassSecurityInfo from AccessControl.class_init import InitializeClass @@ -584,11 +585,25 @@ cfg = getConfiguration() f = os.path.join(cfg.clienthome, '%s.%s' % (id, suffix)) -if toxml: -exportXML(ob._p_jar, ob._p_oid, f) -else: -ob._p_jar.exportFile(ob._p_oid, f) +ob = aq_base(ob) +parent = getattr(ob, '__parent__', _marker) +if parent is not _marker: +sp = transaction.savepoint(True) +del ob.__parent__ +# create a savepoint so that the export includes the version +# without a __parent__ pointer +transaction.savepoint(True) +try: +if toxml: +exportXML(ob._p_jar, ob._p_oid, f) +else: +ob._p_jar.exportFile(ob._p_oid, f) +finally: +if parent is not _marker: +# roll back so that we don't actually remove the __parent__ +sp.rollback() + if REQUEST is not None: return self.manage_main(self, REQUEST, manage_tabs_message= ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py use non-optimistic savepoints; thx elro hannosch
Log message for revision 120869: use non-optimistic savepoints; thx elro hannosch Changed: U Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py -=- Modified: Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py === --- Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py 2011-03-11 15:16:26 UTC (rev 120868) +++ Zope/branches/davisagli-exclude-parent-pointers-from-export/src/OFS/ObjectManager.py 2011-03-11 15:39:28 UTC (rev 120869) @@ -589,11 +589,11 @@ ob = aq_base(ob) parent = getattr(ob, '__parent__', _marker) if parent is not _marker: -sp = transaction.savepoint(True) +sp = transaction.savepoint() del ob.__parent__ # create a savepoint so that the export includes the version # without a __parent__ pointer -transaction.savepoint(True) +transaction.savepoint() try: if toxml: exportXML(ob._p_jar, ob._p_oid, f) ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call
On 3/1/11 11:57 AM, Christian Zagrodnick wrote: This change introduces a regression when calling unicode on wrapped objects that implement __str__ but not __unicode__. Essentially it is now doing the equivalent of str(aq_base(obj)) ... __str__ used to get a wrapped object as 'self', but now it is unwrapped. Here's a failing test that can be added to Acquisition's TestUnicode test case to demonstrate the issue: def test_str_fallback_is_still_wrapped(self): class A(Acquisition.Implicit): def __str__(self): return str(len(Acquisition.aq_chain(self))) wrapped = A().__of__(A()) self.assertEqual(u'2', unicode(wrapped)) This is currently causing some regressions in Plone tests. I'll have a look at it. Thanks for spotting that. Fixed in r120651 (trunk) - Fixed bug: When an object did not implement ``__unicode__``, calling ``unicode(wrapped)`` was calling ``__str__`` with an unwrapped ``self``. Is the situation with Plone better now? Yes, this fixes the test failures we were seeing before. Thanks! David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Acquisition wrapped objects do not behave well on unicode call
On 2/20/11 1:32 AM, Christian Zagrodnick wrote: On 2011-02-19 17:17:44 +0100, Hanno Schlichting said: On Thu, Feb 17, 2011 at 8:27 AM, Christian Zagrodnickc...@gocept.com wrote: On 2011-02-16 22:22:53 +0100, Hanno Schlichting said: svn+ssh://svn.zope.org/repos/main/Acquisition/branches/zagy-unicode-should-be-called Sure. I'll review, merge and release. Should be sometime this week, cannot promise a day. Branch reviewed, merged and released in Acquisition 2.13.6. Could you remove the merged branch once you updated your buildout config? Done. Thanks for releasing! This change introduces a regression when calling unicode on wrapped objects that implement __str__ but not __unicode__. Essentially it is now doing the equivalent of str(aq_base(obj)) ... __str__ used to get a wrapped object as 'self', but now it is unwrapped. Here's a failing test that can be added to Acquisition's TestUnicode test case to demonstrate the issue: def test_str_fallback_is_still_wrapped(self): class A(Acquisition.Implicit): def __str__(self): return str(len(Acquisition.aq_chain(self))) wrapped = A().__of__(A()) self.assertEqual(u'2', unicode(wrapped)) This is currently causing some regressions in Plone tests. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Sprints at PyCon
On 2/9/11 10:07 PM, Christian Theune wrote: Hi, I'll be at PyCon during the sprints. As promised from the tasks last year, I'd be happy to organize Zope sprinting activity. Who's coming? Who's interested? Any topic suggestions? Elizabeth Leddy and I will be there and were thinking of doing some work on improving the state of utilities for managing and introspecting the ZODB. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Good storage/system for sessions
On Jan 5, 2011, at 12:04 AM, li...@nidelven-it.no li...@nidelven-it.no wrote: Hi. We've experienced some problems with the Transcience/SESSION system, where KeyErrors can pop up for unknown reasons. Therefore, I was thinking of writing/using a custom session system, which doesn't do anything magical, just stores it into some kind of database. It would have to support multiple ZEO clients, and I'm thinking it should also respect the transaction machinery, so that if something fails, the changes are rolled back. I've thought of different approaches, but right now, the best approach seems to be a separate database file, in FileStorage, BSDDB or some such variant, mounted at the point /session for example. Then have 3 methods/functions which set, get and delete entries in the storage as necessary. Every user gets a unique cookie and corresponding place in the database. What's the recommended way to handle up to many, many small objects with frequent writes? Am I making unecessary work for me here, or could such a system be useful? Has something like it been made before? Is it better to test and fix the Transcience/SESSION system? Take a look at collective.beaker -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 3 porting sprint?
On 12/2/10 5:39 AM, Lennart Regebro wrote: On Fri, Nov 26, 2010 at 07:26, Ross Patterson m...@rpatterson.net wrote: Who would be interested in a sprint, when, where and how? I'd be interested in remote sprinting. I'm available now, FWIW. OK, so it's me and you then. :-) Let's talk in January about doing something and staying online at the same time during some specified period. I will be at PyCon and would be up for doing some sprinting on it then, but probably can't commit time otherwise. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form buildout broken
On 11/22/10 2:24 AM, Marius Gedminas wrote: Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest to make it optional, since omelette is rarely necessary for development, it's more of a convenience. Print a warning skipping omelette symlink tree construction because junction.exe is not present in %PATH% and continue. Just my €0.02. I think this makes sense, and just released collective.recipe.omelette 0.10 which should give a warning rather than aborting if junction.exe is missing on Windows. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] urllib.urlopen inside a python-script? alternatives?
urlopen is restricted python. You will need to create file system script (a product) (or external script) in order to use it. On Mon, Nov 15, 2010 at 8:43 AM, stepha...@gmx.net wrote: Hello, I'm trying to use facebook's single-sign-on mechanism with zope and querying account information for logged in facebook-users from within zope. For this I need to send url-requests from my zope-server to the facebook-servers and read the response. I tried to test the concept with a python-script: ## import urllib cookie= request[fbs_ + the application id] args=dict(map(lambda x:x.split('='),cookie.split(''))) url=https://graph.facebook.com/me?access_token=+args['access_token'] file = urllib.urlopen(url) resp=file.read() file.close() return args,url,resp ## When running this an authentication-window pops up - and subsequently tells me: --- Error Type: Unauthorized Error Value: You are not allowed to access 'urlopen' in this context --- So the problem is with opening the external-url I suppose ... What's the Zope-way of doing this? - how can I tell it to get read information of another URL? thanks, stephan ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) -- David Bear College of Public Programs at ASU 602-494-0424 ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] Zope 2.13.0 final released
On 11/5/10 10:05 AM, Tres Seaver wrote: On 11/05/2010 12:42 PM, Hanno Schlichting wrote: On behalf of the Zope 2 developers community I am pleased to announce the official release of Zope 2.13.0. Major changes: - Supports Python 2.6 and 2.7 - Includes ZODB 3.10 - which adds multi-threading to the ZEO server - Contains WSGI support - Ships with the Zope Toolkit 1.0 - A number of performance improvements in ZCatalog - lots of other smaller fixes and features For more details, check: http://docs.zope.org/zope2/releases/2.13/WHATSNEW.html Release notes: http://docs.zope.org/zope2/releases/2.13/CHANGES.html If you have found a bug, please report it on Launchpad: https://bugs.launchpad.net/zope2/ I would like to thank all people having contributed to this release. Special thanks to Tres Seaver for bringing WSGI support to Zope 2, Jens Vagelpohl for his tireless bug-fixing efforts and Yvo Schubbe for testing the pre-releases against CMF and helping out with bug fixes and some new features. Many thanks to Hanno for the quality and quantity of his efforts as the Zope2 release manager. Hanno, you rock! +1 :) -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and stratgies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.13 - release candidate blockers
On 10/18/10 1:20 PM, Tres Seaver wrote: On 10/17/2010 10:10 AM, Hanno Schlichting wrote: Hi. With the release of both a final ZODB 3.10 and the ZTK 1.0, we are good to go on a release candidate for Zope 2.13. There's currently two bugs I consider blockers for the release candidate: - zopectl start - doen't work (https://bugs.launchpad.net/zope2/+bug/628448) - Zope2 egg is not available in index (https://bugs.launchpad.net/zope2/+bug/653546) I will take care of the egg in index problem. If anyone has time to look into the zopectl problem, that would be much appreciated. Once this problem is solved I'll release a rc1 and if no problems are found a final release a week after. Hmm, another note here: davisagli fixed this bug on the 2.12 bracnh two weeks after it was checked in (a year ago now). Somehow, that fix didn't get propagated to the trunk. Oops! Sorry I missed that; thanks for taking care of it. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org We're celebrating 15 years! Come to our big party. http://groundwire.org/events/groundwires-15th-anniversary-party ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 20% slower than Zope 2.9?!
On 10/11/10 5:39 AM, Chris Withers wrote: On 11/10/2010 13:32, Hanno Schlichting wrote: My only guess here is that you are calling a lot of page templates and those have gotten slower. When we switched to Unicode based templates in Zope 2.10, that move has of course cost some performance. Dealing with Unicode instead of bytes is always slower. If you want to improve rendering times and your analysis shows page templates to be the problem, try Chameleon. Yes, this is my guess too. Are there any docs on how to get Chameleon to work with classic, ZODB-based page templates? Just use cmf.pt: http://pypi.python.org/pypi/cmf.pt -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org We're celebrating 15 years! Come to our big party. http://groundwire.org/events/groundwires-15th-anniversary-party ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/trunk/ copy the list of packages to initialize. install_package calls package_initialized which removes from the list
Log message for revision 116995: copy the list of packages to initialize. install_package calls package_initialized which removes from the list Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/src/OFS/Application.py -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2010-09-27 22:26:34 UTC (rev 116994) +++ Zope/trunk/doc/CHANGES.rst 2010-09-28 03:17:49 UTC (rev 116995) @@ -11,6 +11,9 @@ Bugs Fixed ++ +- Avoid iterating over the list of packages to initialize while it is being + mutated, which was skipping some packages. + - Fixed two unit tests that failed on fast Windows machines. - Fixed OverflowError in Products.ZCatalog.Lazy on 64bit python Modified: Zope/trunk/src/OFS/Application.py === --- Zope/trunk/src/OFS/Application.py 2010-09-27 22:26:34 UTC (rev 116994) +++ Zope/trunk/src/OFS/Application.py 2010-09-28 03:17:49 UTC (rev 116995) @@ -535,7 +535,7 @@ folder_permissions, raise_exc=debug_mode) # Delayed install of packages-as-products -for module, init_func in get_packages_to_initialize(): +for module, init_func in tuple(get_packages_to_initialize()): install_package(app, module, init_func, raise_exc=debug_mode) Products.meta_types=Products.meta_types+tuple(meta_types) ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] Extending Zope2 bin/instance run
On Sep 3, 2010, at 12:50 AM, Wichert Akkerman wich...@wiggy.net wrote: I have noticed that now that we are almost exclusively using eggs to distribute our software using bin/instance run has become difficult: often the script you want to run is located inside an egg which makes to path to it hard to predict. This is not the most user friendly command: bin/instance run eggs/my.package-*/my/package/script.py If a user is using a shared egg directory from zc.buildout or something else the egg can be anywhere on the filesystem, making it next to impossible to explain to users. I am considering to modify bin/instance run to check if its first argument is a filesystem path, and if not consider the argument to be a dotted name of a callable which should be invoke. That way backwards compatibility remains, but you can now also do this: bin/instance run my.package.script.main I am not sure if this is best done in plone.recipe.zope2instance or Zope2.Startup.zopectl. They have differing versions of ZopeCmd. Perhaps the plone.recipe.zope2instance code should be merged into Zope2's original as well? At some point I made it possible to add additional bin/instance commands via a plone.recipe.zope2instance entry point. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/hotfixes/Products.Zope_Hotfix_CVE_2010_3198/tags/ tags
Log message for revision 116162: tags Changed: A Zope/hotfixes/Products.Zope_Hotfix_CVE_2010_3198/tags/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/hotfixes/Products.Zope_Hotfix_CVE_2010_3198/tags/1.0/ Tagged Products.Zope_Hotfix_CVE_2010_3198 1.0.
Log message for revision 116163: Tagged Products.Zope_Hotfix_CVE_2010_3198 1.0. Changed: A Zope/hotfixes/Products.Zope_Hotfix_CVE_2010_3198/tags/1.0/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] (Zope2) a proposed tweak to assigning default roles to permissions
On 8/19/10 12:46 AM, Hanno Schlichting wrote: Hi. On Thu, Aug 19, 2010 at 6:15 AM, David Glick davidgl...@groundwire.org wrote: As an alternative to requiring calling setDefaultRoles/addPermission at import time, I suggest that we add an optional roles attribute to the permission directive. This would then be used when the directive is executed, instead of the current hard-coded Manager setting. Examples: !-- a new permission with 2 default roles -- permission id=my.NewPermission title=My new permission roles=Manager SiteAdmin/ !-- a new permission with Manager as the sole, implicit role (backwards-compatible) -- permission id=my.OtherPermission title=My other permission/ Can roles currently contain whitespace? Like Awesome People? If so, we should go for nested nodes: permission id=my.NewPermission title=My new permission roleManager/role roleSiteAdmin/role roleAwesome People/role /permission I think this matches the style of some of the GenericSetup handlers which deal with permissions. Implemented at svn+ssh://svn.zope.org/repos/main/AccessControl/branches/davisagli-permission-directive -- can someone please review? Also, where should I document this addition? thanks, -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] (Zope2) a proposed tweak to assigning default roles to permissions
Background: In Zope 2 prior to Zope 2.12, registering a new permission involved the following (usually behind-the-scenes) steps: 1. adding the permission name to the AccessControl.Permission._registeredPermissions dictionary 2. adding a tuple to the Products.__ac_permissions__ list including the permission name and default roles 3. setting a attribute (with name equal to a mangled version of the permission name) of AccessControl.Permission.ApplicationDefaultPermissions to the default roles 4. registering the permission as a Zope 3 permission using the permission ZCML directive In practice in CMF-based applications, the first 3 items of this list were often accomplished by a call (usually during product initialization) to Products.CMFCore.permissions.setDefaultRoles. So for a developer adding a new permission, there were generally 2 tasks required (calling setDefaultRoles and calling the permission directive). In Zope 2.12, the situation improved. There is now an event handler which automatically performs steps #1-3 when a permission is registered using the permission directive, setting the default role to Manager. Unfortunately, this makes things tricky if one wants to register a permission with a different set of default roles. That's because setDefaultRoles (and its new incarnation as AccessControl.Permission.addPermission in Zope 2.13) abort if you try to register a permission that is already registered, so it needs to be called prior to the execution of ZCML actions -- so import time is the only option. Proposal: As an alternative to requiring calling setDefaultRoles/addPermission at import time, I suggest that we add an optional roles attribute to the permission directive. This would then be used when the directive is executed, instead of the current hard-coded Manager setting. Examples: !-- a new permission with 2 default roles -- permission id=my.NewPermission title=My new permission roles=Manager SiteAdmin/ !-- a new permission with Manager as the sole, implicit role (backwards-compatible) -- permission id=my.OtherPermission title=My other permission/ Thoughts? One downside is that we would need to override the permission directive instead of using the implementation in zope.security. On the other hand, it's not a complicated directive. thanks for your consideration, -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] (Zope2) a proposed tweak to assigning default roles to permissions
Proposal: As an alternative to requiring calling setDefaultRoles/addPermission at import time, I suggest that we add an optional roles attribute to the permission directive. This would then be used when the directive is executed, instead of the current hard-coded Manager setting. Examples: This is a proposal to implement this for Zope 2.13, btw. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] vocabularies missing wihtout zope.app.schema
On 7/21/10 6:19 PM, Patrick Gerken wrote: On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting ha...@hannosch.eu wrote: On Mon, Jan 11, 2010 at 4:31 PM, Roger d...@projekt01.ch wrote: The zope.componentvocabulary package defines some basic vocabulary (factory) classes. Probably we should move the zope/app/schema/vocabulary.py to this package as registry.py. If it doesn't introduce new dependencies, that sounds good. Hi, with the newest plone4 beta there is an empty vocabulary registry because no package imports zope.app.schema any longer. I am not sure if the registry from zope.app.schema belongs to zope.componentvocabulary. After all zope.componentvocabulary provides vocabularies for components while zope.app.schema replaces the current, non component based registry with his own one. How about moving the code into zope.schema and make it the default registry if zope.component is available? I ran into this yesterday. It is already fixed in lastest Zope 2.12 and Plone trunk (thanks Hanno). The vocab registry that looks up vocabularies as components is now located in Products.Five.schema (to avoid depending on zope.app.schema). For tests it is now initialized in latest Products.PloneTestCase. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/trunk/ we need a newer AccessControl
Log message for revision 114792: we need a newer AccessControl Changed: U Zope/trunk/buildout.cfg U Zope/trunk/setup.py -=- Modified: Zope/trunk/buildout.cfg === --- Zope/trunk/buildout.cfg 2010-07-16 06:10:42 UTC (rev 114791) +++ Zope/trunk/buildout.cfg 2010-07-16 06:16:32 UTC (rev 114792) @@ -18,8 +18,8 @@ wsgi sources-dir = develop auto-checkout = +AccessControl - [test] recipe = zc.recipe.testrunner eggs = Zope2 Modified: Zope/trunk/setup.py === --- Zope/trunk/setup.py 2010-07-16 06:10:42 UTC (rev 114791) +++ Zope/trunk/setup.py 2010-07-16 06:16:32 UTC (rev 114792) @@ -39,7 +39,7 @@ namespace_packages=['Products', 'Shared', 'Shared.DC'], package_dir={'': 'src'}, install_requires=[ - 'AccessControl', + 'AccessControl=2.13.2dev', 'Acquisition', 'DateTime', 'DocumentTemplate', ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/ make sure that the browser:view directive doesn't clobber security declarations for attributes which are not included in allowed_attributes or allowed_interfac
Log message for revision 114789: make sure that the browser:view directive doesn't clobber security declarations for attributes which are not included in allowed_attributes or allowed_interface but which already have security declarations in a base class's security info. This is needed to provide access to, e.g., restrictedTraverse on views that subclass Traversable Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py U Zope/branches/2.12/src/Products/Five/browser/tests/pages.py U Zope/branches/2.12/src/Products/Five/browser/tests/pages.txt U Zope/branches/2.12/src/Products/Five/browser/tests/pages.zcml U Zope/branches/2.12/src/Products/Five/security.py -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-07-16 05:56:26 UTC (rev 114789) @@ -11,6 +11,12 @@ Bugs Fixed ++ +- Fix support for non-public permission attributes in the + browser:view directive so that attributes which are not included in + allowed_interface or allowed_attributes but which have declarations from a + base class's security info don't get their security overwritten to be + private. + - LP #143755: Also catch TypeError when trying to determine an indexable value for an object in PluginIndexes.common.UnIndex Modified: Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py === --- Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-07-16 05:56:26 UTC (rev 114789) @@ -315,7 +315,7 @@ _context.action( discriminator = ('five:protectName', newclass, attr), callable = protectName, -args = (newclass, attr, CheckerPrivateId) +args = (newclass, attr, CheckerPrivateId, False) ) # Protect the class Modified: Zope/branches/2.12/src/Products/Five/browser/tests/pages.py === --- Zope/branches/2.12/src/Products/Five/browser/tests/pages.py 2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/src/Products/Five/browser/tests/pages.py 2010-07-16 05:56:26 UTC (rev 114789) @@ -17,6 +17,7 @@ from Products.Five import BrowserView from Products.Five.browser.pagetemplatefile import ViewPageTemplateFile +from OFS.SimpleItem import SimpleItem class SimpleView(BrowserView): More docstring. Please Zope @@ -40,6 +41,11 @@ def __call__(self): return uI was __call__()'ed +class PermissionView(BrowserView, SimpleItem): + +def __call__(self): +return uI was __call__()'ed + class CallTemplate(BrowserView): __call__ = ViewPageTemplateFile('falcon.pt') Modified: Zope/branches/2.12/src/Products/Five/browser/tests/pages.txt === --- Zope/branches/2.12/src/Products/Five/browser/tests/pages.txt 2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/src/Products/Five/browser/tests/pages.txt 2010-07-16 05:56:26 UTC (rev 114789) @@ -275,6 +275,13 @@ aq_parent(aq_inner(context)) Folder at /test_folder_1_ +Make sure that methods which are not included in the allowed interface or +attributes, but which already had security declarations from a base class, +don't get those declarations overridden to be private. (The roles for +restrictedTraverse should be None, indicating it is public.) + + view.restrictedTraverse__roles__ + High-level security --- Modified: Zope/branches/2.12/src/Products/Five/browser/tests/pages.zcml === --- Zope/branches/2.12/src/Products/Five/browser/tests/pages.zcml 2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/src/Products/Five/browser/tests/pages.zcml 2010-07-16 05:56:26 UTC (rev 114789) @@ -237,7 +237,7 @@ browser:view name=permission_view for=Products.Five.tests.testing.simplecontent.ISimpleContent - class=.pages.CallView + class=.pages.PermissionView permission=zope2.ViewManagementScreens / Modified: Zope/branches/2.12/src/Products/Five/security.py === --- Zope/branches/2.12/src/Products/Five/security.py2010-07-15 19:52:12 UTC (rev 114788) +++ Zope/branches/2.12/src/Products/Five/security.py2010-07-16 05:56:26 UTC (rev 114789) @@ -127,12 +127,15 @@ setattr(klass, '__security__', security) return security -def protectName(klass, name, permission_id): +def protectName(klass, name, permission_id,
[Zope-Checkins] SVN: Zope/trunk/versions.cfg update RestrictedPython version
Log message for revision 114387: update RestrictedPython version Changed: U Zope/trunk/versions.cfg -=- Modified: Zope/trunk/versions.cfg === --- Zope/trunk/versions.cfg 2010-07-09 17:12:00 UTC (rev 114386) +++ Zope/trunk/versions.cfg 2010-07-09 17:24:21 UTC (rev 114387) @@ -22,7 +22,7 @@ ZopeUndo = 2.12.0 # ZTK KGS overrides -RestrictedPython = 3.6.0a1 +RestrictedPython = 3.6.0 ZODB3 = 3.10.0b1 # Zope2 dependencies ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] audit of RestrictedPython for Python 2.7
I am done (as far as I can tell) evaluating RestrictedPython to see if changes are needed to support Python 2.7. This is the first time I have done this, so would appreciate if someone else can look over my work to make sure I'm not missing something important. I'll describe my process and findings below. The basic summary is that Python 2.7 adds a small number of syntactic features and they are already handled adequately by RestrictedPython. I added some tests for these on a branch, http://svn.zope.org/repos/main/RestrictedPython/branches/davisagli-python27, which I can merge once someone else has looked over them. In addition, I discovered the omission of a name check for the from x import y style import; this is also fixed on the branch. To go into detail... I started by reading RestrictedPython (henceforth referred to as RP) to familiarize myself with how it works. Next I read the What's New in Python 2.7 document and noted features that might require changes in RP. Then I went through each of these and looked at the corresponding changes in the Python compiler, bytecode generator and evaluator to further check on whether changes were needed. Here are the items I checked and my conclusions... - dict and set comprehensions: These need to use RP's safe _getitem_ to iterate. This was already taken care of because these new comprehensions use the same ListCompFor AST node that list comprehensions do. - set literals: These build a new set based on the result of evaluating other AST nodes that RP already protects, so should be safe. - multiple context managers in one with statement: I wrote a test to confirm that the existing name check for context managers still works when there are multiple ones. - the 'with' statement now uses a new opcode SETUP_WITH that does an unprotected lookup of the '__enter__' and '__exit__' methods of the context manager. I don't think this is a problem, since methods starting with an underscore can't be defined in RP. - dictionary views: these don't introduce new builtins or syntax, so I don't think changes are necessary. To allow access to them in RP in Zope 2 we would need to adjust the dict method whitelist in AccessControl.ZopeGuards to allow viewitems, viewkeys, and viewvalues. - new builtins memoryview, bytes, and bytearray: For now I punted and these are not included in RP's safe_builtins list. memoryview and bytearray should probably not be added. bytes is just a synonym for str in Python 2.7 afaict, so would probably be okay to add. - explicit relative imports (from .x import y): These are covered by the name check I added (as noted above in the summary) for from x import y imports in general. - except x as y: Added a test to show that this is already covered. Finally, to double-check my work I did diffs of Lib/compiler/ast.py and Python/ceval.c in the Python source to check for any new AST nodes or opcodes that I had overlooked above. This didn't yield any new concerns that I hadn't already considered. peace, David David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 [http://gw-logo.s3.amazonaws.com/groundwire-logo-270-noclear.png]http://groundwire.org/?utm_source=Groundwire.org%2BEmailutm_medium=Emailutm_campaign=Logo Sign up for Groundwire News!http://groundwire.org/email-capture?utm_source=Groundwire.org-emailutm_medium=Emailutm_content=Sign-up-for-groundwire-newsutm_campaign=email-signature Tips, tools and news delivered directly to your inbox. http://groundwire.org/email-capture?utm_source=Groundwire.org-emailutm_medium=Emailutm_content=Sign-up-for-groundwire-newsutm_campaign=email-signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/branches/2.12/ fix regression in traversing to 'macros' on template-based browser views, which crept in somewhere on the way to 2.12
Log message for revision 110119: fix regression in traversing to 'macros' on template-based browser views, which crept in somewhere on the way to 2.12 Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py U Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-03-23 21:12:19 UTC (rev 110118) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-03-23 21:43:11 UTC (rev 110119) @@ -20,6 +20,8 @@ Bugs Fixed ++ +- Restore ability to traverse to 'macros' on template-based browser views. + - Protect ZCTextIndex's clear method against storing Acquisition wrappers. - LP #195761: fixed ZMI XML export / import and restored it to the UI. Modified: Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py === --- Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-03-23 21:12:19 UTC (rev 110118) +++ Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-03-23 21:43:11 UTC (rev 110119) @@ -421,6 +421,8 @@ raise NotFound(self, name, request) def __getitem__(self, name): +if name == 'macros': +return self.index.macros return self.index.macros[name] def __call__(self, *args, **kw): Modified: Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py === --- Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 21:12:19 UTC (rev 110118) +++ Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 21:43:11 UTC (rev 110119) @@ -41,6 +41,12 @@ index.macros = {} index.macros['aaa'] = aaa = object() self.failUnless(view['aaa'] is aaa) + +def test__getitem__gives_shortcut_to_index_macros(self): +view = self._makeOne() +view.index = index = DummyTemplate() +index.macros = {} +self.failUnless(view['macros'] is index.macros) def test___call___no_args_no_kw(self): view = self._makeOne() ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py fix obvious NameError
Log message for revision 110120: fix obvious NameError Changed: U Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py -=- Modified: Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py === --- Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-03-23 21:43:11 UTC (rev 110119) +++ Zope/branches/2.12/src/Products/Five/browser/metaconfigure.py 2010-03-23 21:48:57 UTC (rev 110120) @@ -230,7 +230,7 @@ if view is not None: return view -raise NotFoundError(self, name, request) +raise NotFound(self, name, request) cdict['publishTraverse'] = publishTraverse ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py avoid test method name collision
Log message for revision 110121: avoid test method name collision Changed: U Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py -=- Modified: Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py === --- Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 21:48:57 UTC (rev 110120) +++ Zope/branches/2.12/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 21:52:11 UTC (rev 110121) @@ -69,7 +69,7 @@ self.failUnless(result is index) self.assertEqual(index._called_with, ((), {'foo': 'bar'})) -def test___call___no_args_no_kw(self): +def test___call___w_args_w_kw(self): view = self._makeOne() view.index = index = DummyTemplate() result = view('abc', foo='bar') ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/Products/Five/browser/ merge r110118-110121 from 2.12 branch
Log message for revision 110122: merge r110118-110121 from 2.12 branch Changed: U Zope/trunk/src/Products/Five/browser/metaconfigure.py U Zope/trunk/src/Products/Five/browser/tests/test_metaconfigure.py -=- Modified: Zope/trunk/src/Products/Five/browser/metaconfigure.py === --- Zope/trunk/src/Products/Five/browser/metaconfigure.py 2010-03-23 21:52:11 UTC (rev 110121) +++ Zope/trunk/src/Products/Five/browser/metaconfigure.py 2010-03-23 22:01:16 UTC (rev 110122) @@ -231,7 +231,7 @@ if view is not None: return view -raise NotFoundError(self, name, request) +raise NotFound(self, name, request) cdict['publishTraverse'] = publishTraverse @@ -422,6 +422,8 @@ raise NotFound(self, name, request) def __getitem__(self, name): +if name == 'macros': +return self.index.macros return self.index.macros[name] def __call__(self, *args, **kw): Modified: Zope/trunk/src/Products/Five/browser/tests/test_metaconfigure.py === --- Zope/trunk/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 21:52:11 UTC (rev 110121) +++ Zope/trunk/src/Products/Five/browser/tests/test_metaconfigure.py 2010-03-23 22:01:16 UTC (rev 110122) @@ -41,6 +41,12 @@ index.macros = {} index.macros['aaa'] = aaa = object() self.failUnless(view['aaa'] is aaa) + +def test__getitem__gives_shortcut_to_index_macros(self): +view = self._makeOne() +view.index = index = DummyTemplate() +index.macros = {} +self.failUnless(view['macros'] is index.macros) def test___call___no_args_no_kw(self): view = self._makeOne() @@ -63,7 +69,7 @@ self.failUnless(result is index) self.assertEqual(index._called_with, ((), {'foo': 'bar'})) -def test___call___no_args_no_kw(self): +def test___call___w_args_w_kw(self): view = self._makeOne() view.index = index = DummyTemplate() result = view('abc', foo='bar') ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope] preventing form submission
Is there a step by step guide to document how to do this? On Tue, Feb 2, 2010 at 6:03 PM, Shane Hathaway sh...@hathawaymix.orgwrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garry Saddington wrote: Has anyone any suggestions as to how to prevent form submission by the using pressing the refresh or back buttons? Issue a redirect from the POST handler: the browser won't land again on the original POST target URL, but only only on the redirected page, or the original form. +1, I've been happy with this technique. Shane ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) -- David Bear College of Public Programs at ASU 602-494-0424 ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/branches/2.10/ look for ZEXP imports in the clienthome dir too
Log message for revision 107525: look for ZEXP imports in the clienthome dir too Changed: U Zope/branches/2.10/doc/CHANGES.txt U Zope/branches/2.10/lib/python/OFS/ObjectManager.py -=- Modified: Zope/branches/2.10/doc/CHANGES.txt === --- Zope/branches/2.10/doc/CHANGES.txt 2010-01-01 23:17:41 UTC (rev 107524) +++ Zope/branches/2.10/doc/CHANGES.txt 2010-01-02 03:20:02 UTC (rev 107525) @@ -8,6 +8,10 @@ Bugs fixed + - Also look for ZEXP imports within the clienthome directory. This +provides a place to put imports that won't be clobbered by buildout +in a buildout-based Zope instance. + - LP #143444: add labels to checkboxes / radio buttons on import / export form. Modified: Zope/branches/2.10/lib/python/OFS/ObjectManager.py === --- Zope/branches/2.10/lib/python/OFS/ObjectManager.py 2010-01-01 23:17:41 UTC (rev 107524) +++ Zope/branches/2.10/lib/python/OFS/ObjectManager.py 2010-01-02 03:20:02 UTC (rev 107525) @@ -642,6 +642,8 @@ paths = [cfg.zopehome] if not cfg.instancehome in paths: paths.append(cfg.instancehome) +if not cfg.clienthome in paths: +paths.append(cfg.clienthome) for impath in paths: directory = os.path.join(impath, 'import') if not os.path.isdir(directory): ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.11/ merge r107525 from Zope 2.10
Log message for revision 107526: merge r107525 from Zope 2.10 Changed: U Zope/branches/2.11/doc/CHANGES.txt U Zope/branches/2.11/lib/python/OFS/ObjectManager.py -=- Modified: Zope/branches/2.11/doc/CHANGES.txt === --- Zope/branches/2.11/doc/CHANGES.txt 2010-01-02 03:20:02 UTC (rev 107525) +++ Zope/branches/2.11/doc/CHANGES.txt 2010-01-02 03:36:34 UTC (rev 107526) @@ -8,6 +8,10 @@ Bugs Fixed + - Also look for ZEXP imports within the clienthome directory. This +provides a place to put imports that won't be clobbered by buildout +in a buildout-based Zope instance. + - LP #143444: add labels to checkboxes / radio buttons on import / export form. Modified: Zope/branches/2.11/lib/python/OFS/ObjectManager.py === --- Zope/branches/2.11/lib/python/OFS/ObjectManager.py 2010-01-02 03:20:02 UTC (rev 107525) +++ Zope/branches/2.11/lib/python/OFS/ObjectManager.py 2010-01-02 03:36:34 UTC (rev 107526) @@ -647,6 +647,8 @@ paths = [cfg.zopehome] if not cfg.instancehome in paths: paths.append(cfg.instancehome) +if not cfg.clienthome in paths: +paths.append(cfg.clienthome) for impath in paths: directory = os.path.join(impath, 'import') if not os.path.isdir(directory): ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.10/lib/python/OFS/ObjectManager.py missed one change
Log message for revision 107527: missed one change Changed: U Zope/branches/2.10/lib/python/OFS/ObjectManager.py -=- Modified: Zope/branches/2.10/lib/python/OFS/ObjectManager.py === --- Zope/branches/2.10/lib/python/OFS/ObjectManager.py 2010-01-02 03:36:34 UTC (rev 107526) +++ Zope/branches/2.10/lib/python/OFS/ObjectManager.py 2010-01-02 03:39:00 UTC (rev 107527) @@ -599,7 +599,7 @@ raise BadRequest, 'Invalid file name %s' % escape(file) cfg = getConfiguration() -for impath in (cfg.instancehome, cfg.zopehome): +for impath in (cfg.instancehome, cfg.zopehome, cfg.clienthome): filepath = os.path.join(impath, 'import', file) if os.path.exists(filepath): break ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.11/lib/python/OFS/ObjectManager.py missed one change
Log message for revision 107528: missed one change Changed: U Zope/branches/2.11/lib/python/OFS/ObjectManager.py -=- Modified: Zope/branches/2.11/lib/python/OFS/ObjectManager.py === --- Zope/branches/2.11/lib/python/OFS/ObjectManager.py 2010-01-02 03:39:00 UTC (rev 107527) +++ Zope/branches/2.11/lib/python/OFS/ObjectManager.py 2010-01-02 03:39:16 UTC (rev 107528) @@ -604,7 +604,7 @@ raise BadRequest, 'Invalid file name %s' % escape(file) cfg = getConfiguration() -for impath in (cfg.instancehome, cfg.zopehome): +for impath in (cfg.instancehome, cfg.zopehome, cfg.clienthome): filepath = os.path.join(impath, 'import', file) if os.path.exists(filepath): break ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/ merge r107525-107528 from Zope 2.10
Log message for revision 107529: merge r107525-107528 from Zope 2.10 Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/src/OFS/ObjectManager.py -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-01-02 03:39:16 UTC (rev 107528) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-01-02 03:43:32 UTC (rev 107529) @@ -11,6 +11,10 @@ Bugs Fixed ++ +- Also look for ZEXP imports within the clienthome directory. This + provides a place to put imports that won't be clobbered by buildout + in a buildout-based Zope instance. + - Fixed a SyntaxError in utilities/load_site.py script. Features Added Modified: Zope/branches/2.12/src/OFS/ObjectManager.py === --- Zope/branches/2.12/src/OFS/ObjectManager.py 2010-01-02 03:39:16 UTC (rev 107528) +++ Zope/branches/2.12/src/OFS/ObjectManager.py 2010-01-02 03:43:32 UTC (rev 107529) @@ -617,7 +617,6 @@ if dirname: raise BadRequest, 'Invalid file name %s' % escape(file) -cfg = getConfiguration() for impath in self._getImportPaths(): filepath = os.path.join(impath, 'import', file) if os.path.exists(filepath): @@ -663,6 +662,8 @@ paths.append(zopehome) if not cfg.instancehome in paths: paths.append(cfg.instancehome) +if not cfg.clienthome in paths: +paths.append(cfg.clienthome) return paths def list_imports(self): ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ merge r107529 from Zope 2.12
Log message for revision 107530: merge r107529 from Zope 2.12 Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/src/OFS/ObjectManager.py -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2010-01-02 03:43:32 UTC (rev 107529) +++ Zope/trunk/doc/CHANGES.rst 2010-01-02 03:54:08 UTC (rev 107530) @@ -122,6 +122,10 @@ Bugs Fixed ++ +- Also look for ZEXP imports within the clienthome directory. This + provides a place to put imports that won't be clobbered by buildout + in a buildout-based Zope instance. + - LP #143444: add labels to checkboxes / radio buttons on import / export form. Modified: Zope/trunk/src/OFS/ObjectManager.py === --- Zope/trunk/src/OFS/ObjectManager.py 2010-01-02 03:43:32 UTC (rev 107529) +++ Zope/trunk/src/OFS/ObjectManager.py 2010-01-02 03:54:08 UTC (rev 107530) @@ -617,7 +617,6 @@ if dirname: raise BadRequest, 'Invalid file name %s' % escape(file) -cfg = getConfiguration() for impath in self._getImportPaths(): filepath = os.path.join(impath, 'import', file) if os.path.exists(filepath): @@ -663,6 +662,8 @@ paths.append(zopehome) if not cfg.instancehome in paths: paths.append(cfg.instancehome) +if not cfg.clienthome in paths: +paths.append(cfg.clienthome) return paths def list_imports(self): ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope] Session bugs around CAS4PAS integration in Plone
since this presents 2 questions -- I would like to ask more about the first -- of all the CAS pluggins for zope and plone -- which one works best;-) Actually, since we serve content both directly from Zope AND from plone, I need one that works with 'both'... in other words, I need something that works for zope authentication -- as well as plone. Any pointers on which 'single' prooduct package will allow that? On Fri, Dec 18, 2009 at 7:28 AM, Encolpe Degoute encolpe.dego...@quadra-informatique.fr wrote: Hello, These last months we have a random bug around CAS authentication. Preamble: CAS plugins are multiple but all are based on CAS4PAS : - CAS4PAS - Products.CAS4PAS - collective.castle - collective.cas4plone They all doing more or less the same job with different maintainers... They are all in the collective but outside http://svn.plone.org/svn/collective/PASPlugins/ Guys, can we try to work together ? If you only need rights to upload a release on pypi just ask them, don't start a fork. Our problem is user can obtain another session opened with CAS when the server is overloaded. It happens only one the first page loaded for a session and once the user get the session he keeps it until is logout. There is no web cache and Zope serve pages directly to them. There is 4 threads and 5000 objects in session cache. We suspect a session cache bug but we don't know how to debug it as the bug comes randomly when the server is overloaded (more than 5 concurrent users). Any tips to build a test environment for this ? Regards, -- int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\ o, world!\\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);} -+- Dishonorable mention, Obfuscated C Code Contest, 1984 Author requested anonymity -+- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) -- David Bear College of Public Programs at ASU 602-494-0424 ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/branches/2.12/ make zopectl start work again, refs LP #453723
Log message for revision 105113: make zopectl start work again, refs LP #453723 Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/src/Zope2/Startup/zopectl.py -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2009-10-16 21:11:39 UTC (rev 105112) +++ Zope/branches/2.12/doc/CHANGES.rst 2009-10-17 06:41:06 UTC (rev 105113) @@ -25,6 +25,8 @@ - LP #443005: zopectl stop works once more on Windows. +- LP #453723: zopectl start works again on non-Windows platforms. + Zope 2.12.0 final (2009/10/01) --- Modified: Zope/branches/2.12/src/Zope2/Startup/zopectl.py === --- Zope/branches/2.12/src/Zope2/Startup/zopectl.py 2009-10-16 21:11:39 UTC (rev 105112) +++ Zope/branches/2.12/src/Zope2/Startup/zopectl.py 2009-10-17 06:41:06 UTC (rev 105113) @@ -216,6 +216,7 @@ # signal to Zope that it is being managed # (to indicate it's web-restartable) os.putenv('ZMANAGED', '1') +ZDCmd.do_start(self, arg) ## START OF WINDOWS ONLY STUFF ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] Is it all right to merge for unicodeSpliting at ZCTextIndex?
Takeshi Yamamoto wrote: This merge was committed to Zope/branches/2.12 branch successfully. Committed revision 105033. I think this change supposed to be merged from 2.12 branch to the trunk sometime later. So, I assumed that I should not merge this change to the trunk. Please do merge it to trunk also. Otherwise the change won't be included in Zope 2.13 and following. David ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Is it all right to merge for unicodeSpliting at ZCTextIndex?
Takeshi Yamamoto wrote: I would like to merge the following change to the trunk. svn diff -r 104723:104761 svn://svn.zope.org/repos/main/Zope/branches/tyam-unicodeSplitterPatch This change is to add a hook for proper text indexing for Ease Asian Languages(CJK). Is it all right to merge this? Don't you actually want to merge it to the 2.12 branch? David ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] Zope and wxPython interface
What do you gain by doing this? On Wed, Aug 12, 2009 at 2:50 PM, Lumir Jasiok lumir.jas...@vsb.cz wrote: Hi, I need to write an application which will be based on MVC design and will have both web interface and desktop GUI based on wxPython. It is possible to write such an application as standard Zope app and use zope.interfaces package for defining wxPython GUI as other view (I hope that it's called view, I am not sure - I am new in Zope programming)? Or am I totally wrong? Best Regards Lumir Jasiok -- Lumír Jasiok VSB-TU Ostrava - Computer centre Tel: +420 59 732 3189 E-mail: lumir.jas...@vsb.cz http://www.vsb.cz ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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-Checkins] SVN: Zope/branches/2.12/src/Products/PluginIndexes/PathIndex/tests/testPathIndex.py the tests pass fine without this and it is causing test interdependency issues when run along with t
Log message for revision 102622: the tests pass fine without this and it is causing test interdependency issues when run along with the Plone products and ExtendedPathIndex tests Changed: U Zope/branches/2.12/src/Products/PluginIndexes/PathIndex/tests/testPathIndex.py -=- Modified: Zope/branches/2.12/src/Products/PluginIndexes/PathIndex/tests/testPathIndex.py === --- Zope/branches/2.12/src/Products/PluginIndexes/PathIndex/tests/testPathIndex.py 2009-08-09 19:12:55 UTC (rev 102621) +++ Zope/branches/2.12/src/Products/PluginIndexes/PathIndex/tests/testPathIndex.py 2009-08-09 21:14:24 UTC (rev 102622) @@ -18,7 +18,6 @@ import unittest import Testing import Zope2 -Zope2.startup() from Products.PluginIndexes.PathIndex.PathIndex import PathIndex ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [ZWeb] Error Type, IOError, Error Value, [Errno 28] No space left on device
That's pretty much along the lines I was thinking as well when I looked at it real quick this morning. +1 from me, fwiw. --Dave On Aug 6, 2009, at 11:24 AM, Jens Vagelpohl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just want to mention that we will run into space problems again tonight. The ZODB is 32 GB in size, and there's 2 GB space left on the drive. Any repozo run or pack at this point will fail. The only way out I can see involves the following: - delete all repozo backups - pack the database manually - delete Data.fs.old After that repozo will start with a fresh backup. Anyone have any better ideas? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkp69Z4ACgkQRAx5nvEhZLIdzACggnNgk5wp7GIAO4aLX34zJcOD ULEAnjRxhcr9yb9Upc6952bv7eJPMpJD =RjRo -END PGP SIGNATURE- ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web Systems Administrator Zope Corp. 540-361-1722 da...@zope.com ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [ZWeb] Error Type, IOError, Error Value, [Errno 28] No space left on device
Joseph and I both cleaned off some things. I also modified the repozo backup cleanup script to only keep six days of backups, otherwise we would have run out of space again either in a week or the next time the database packed. The major space usage was the Data.fs, the Data.fs.old, and two full FS backups made by repozo. --Dave On Aug 3, 2009, at 1:12 PM, Jens Vagelpohl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 3, 2009, at 18:01 , Andreas Jung wrote: We run out of disk space for the zope.org site. Does this error still occur? I see 12 GB free on that drive, but there's two other people who logged in before me, maybe they deleted something. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkp3GmoACgkQRAx5nvEhZLKJ6QCgiRuvijMieeuzE266cY+DoBen VwIAoJSxTmoe5R5+c4czJaf3UcRSvjhn =Lqqi -END PGP SIGNATURE- ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web Systems Administrator Zope Corp. 540-361-1722 da...@zope.com ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [Zope] Cheap Zope hosting
Check out aclark.net . I have been very pleased with the service and quick responses to my requests. On Fri, Jul 31, 2009 at 7:55 AM, Allen Schmidt Sr. aschm...@fredericksburg.com wrote: Now that HighSpeedRails is closing down at midnight tonight, does anyone have any low-cost suggestions for hosting a handful of low-traffic domains in a single Zope?? Thanks -Allen ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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-dev] unregistering persistent utilities
Is there a recommended way or example code somewhere for removing a utility registration from a persistent component registry, when that utility's module no longer exists? The use case is in Plone, which has a local zope.app.cache.ram.IRAMCache utility. Now that Hanno has factored out the RAM cache into zope.ramcache, we'd like the persistent utility to reference zope.ramcache, so that we can remove our zope.app.cache dependency. I've been trying to make this work using a temporary module alias (code below), but something strange is going on. In particular, unghosting the persistent utilities registry is affecting things somehow...before that happens, doing a repr of IRAMCache gives: (Pdb) zope.app.cache.interfaces.ram.IRAMCache InterfaceClass zope.ramcache.interfaces.ram.IRAMCache ...(what I'd expect, I guess, given my module alias)...but after the registry is unghosted, it gives: (Pdb) zope.app.cache.interfaces.ram.IRAMCache InterfaceClass zope.app.cache.interfaces.ram.IRAMCache ...(which is what I'm actually hoping for, in order to unregister the old utility)...but then I also get: (Pdb) zope.ramcache.interfaces.ram.IRAMCache InterfaceClass zope.app.cache.interfaces.ram.IRAMCache ...(e.g., now accessing it via the new module gives a class that thinks its in the old module) Sorry for the rather muddled description, but I haven't been able to really understand what's going on there yet. So what am I missing or doing wrong? Is there a better way to go about this? def relocateRamCacheUtility(portal): # temporary module alias try: import zope.app.cache old_zope_app_cache = zope.app.cache except ImportError: old_zope_app_cache = None import zope.ramcache zope.app.cache = sys.modules['zope.app.cache'] = zope.ramcache sm = getSiteManager(context=portal) # make sure the persistent utilities registry is unghosted before we # reference the old interface name, as it seems to make a difference in # whether it can be unregistered (WTF?) sm.utilities.changed component = sm.getUtility(zope.app.cache.interfaces.ram.IRAMCache) sm.unregisterUtility(component=component, provided=zope.app.cache.interfaces.ram.IRAMCache) import zope.ramcache import pdb; pdb.set_trace( ) sm.registerUtility(factory=zope.ramcache.ram.RAMCache, provided=zope.ramcache.interfaces.ram.IRAMCache) logger.info('Updated the import location of the local IRAMCache utility.') # reset the module alias zope.app.cache = sys.modules['zope.app.cache'] = old_zope_app_cache thanks, David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ 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-Checkins] SVN: Zope/branches/2.12/setup.py properly declare Products as a namespace package
Log message for revision 101659: properly declare Products as a namespace package Changed: U Zope/branches/2.12/setup.py -=- Modified: Zope/branches/2.12/setup.py === --- Zope/branches/2.12/setup.py 2009-07-06 18:28:30 UTC (rev 101658) +++ Zope/branches/2.12/setup.py 2009-07-06 18:37:44 UTC (rev 101659) @@ -29,6 +29,7 @@ file(os.path.join(doc, CHANGES.rst)).read(), packages=find_packages('src'), +namespace_packages=['Products'], package_dir={'': 'src'}, ext_modules=[ ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/setup.py merge r101659 from the 2.12 branch: properly declare Products as a namespace package
Log message for revision 101661: merge r101659 from the 2.12 branch: properly declare Products as a namespace package Changed: U Zope/trunk/setup.py -=- Modified: Zope/trunk/setup.py === --- Zope/trunk/setup.py 2009-07-06 18:40:29 UTC (rev 101660) +++ Zope/trunk/setup.py 2009-07-06 18:40:32 UTC (rev 101661) @@ -29,6 +29,7 @@ file(os.path.join(doc, CHANGES.rst)).read(), packages=find_packages('src'), +namespace_packages=['Products'], package_dir={'': 'src'}, ext_modules=[ ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope] Getting Auto Increment value
I am working with zope mysql. I have a table with SERIAL column type, I create z-sql method for insert operation, how can I get the value for the auto increment column? I know that in mysql I can call last_insert_id(), how do I call it, should I create another z sql method and if I do, how can I be sure the the value return is for my insert command and not for another. Is there a way to call 2 query from the same z sql method? I am really lost on this, any help will be wellcom. Thank in advanced. ___ 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 )
Re: [Zope-dev] z3c.form 2.0 release?
On May 21, 2009, at 11:09 PM, Malthe Borch wrote: 2009/5/21 David Glick davidgl...@onenw.org: Won't this cause problems if a z3c.form uses a template which calls a macro from a traditional Zope page template? That is, make it impossible to use z3c.form in a site that isn't using z3c.pt for everything? That was the reason for z3c.ptcompat; it lets you use one import-location to switch between the two implementations. Ah, right...I was remembering incorrectly why we were unable to use z3c.ptcompat from within Plone. The actual reason is that it uses ViewPageTemplateFile from z3c.pt when we need it from five.pt (I think...it's been a while). But we were able to work around that by adjusting the custom form and widget template factories in plone.z3cform David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ 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] z3c.form 2.0 release?
On May 21, 2009, at 1:10 AM, Malthe Borch wrote: I think at this point that z3c.form could have a strong dependency on z3c.pt. Complete list of extra packages: Won't this cause problems if a z3c.form uses a template which calls a macro from a traditional Zope page template? That is, make it impossible to use z3c.form in a site that isn't using z3c.pt for everything? David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ 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] need help importing python class into zope 2.11.2
HI I'm new to zope and python, I wrote some basic python class and a test program using this class. The script is working fine when running python from command line. Now I want to uses this class inside zope, I tried to create the script, but it failed with the following error. Line 5: __init__ is an invalid variable name because it starts with _ Can I write a constructor with different name? Please advice what is the correct why to import this class to zope Thanks Dganit ___ 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 )
Re: [Zope] SSL/https
So you are not using apache or IIS to front end zope in order to provide the ssl/tls transport. I know there was a project to provide native tls for zope -- but I don't think you will find that it is wide spread. You might take a look at http://www.zope.org/Members/lerouxa/zopehttps/infoand http://sandbox.rulemaker.net/ngps/zope/zssl/ search zope.org basically returns info about m2crypt and using apache to front end zope. I think the best supported option will be to front end zope with apache or iis. On Mon, Apr 13, 2009 at 7:57 AM, Catherine E. Reinehr crein...@huntingdon.edu wrote: Right, sorry. Here you go: Zope Version (Zope 2.6.2 (binary release, python 2.1, win32-x86), python 2.1.3, win32) Python Version 2.1.3 (#35, Apr 8 2002, 17:47:50) [MSC 32 bit (Intel)] System Platform win32 - Catherine E. Reinehr Webmaster Director of Publications Huntingdon College 1500 E. Fairview Ave. Montgomery, AL 36106 (334) 833-4429 / Flowers 218B *From:* David Bear [mailto:david.b...@asu.edu] *Sent:* Thursday, April 09, 2009 7:44 PM *To:* crein...@huntingdon.edu *Cc:* zope@zope.org *Subject:* Re: [Zope] SSL/https memories are short. you need to remind us the exact configuration. Are you using apache to front end zope? On Tue, Apr 7, 2009 at 7:54 AM, Catherine E. Reinehr crein...@huntingdon.edu wrote: Good morning, You might remember my asking for help last month with generating a CSR and installing an SSL certificate. I did get that done, and now I have a new problem. If I replace http://; with https://; in the address, I get a file not found error. What do I need to do to make sure our application for admission is secure? I'm sort of out of my league here. Thanks for whatever help you can give me :) Cat - Catherine E. Reinehr Webmaster Director of Publications Huntingdon College 1500 E. Fairview Ave. Montgomery, AL 36106 (334) 833-4429 / Flowers 218B ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 )
Re: [Zope] SSL/https
memories are short. you need to remind us the exact configuration. Are you using apache to front end zope? On Tue, Apr 7, 2009 at 7:54 AM, Catherine E. Reinehr crein...@huntingdon.edu wrote: Good morning, You might remember my asking for help last month with generating a CSR and installing an SSL certificate. I did get that done, and now I have a new problem. If I replace http://; with https://; in the address, I get a file not found error. What do I need to do to make sure our application for admission is secure? I'm sort of out of my league here. Thanks for whatever help you can give me :) Cat - Catherine E. Reinehr Webmaster Director of Publications Huntingdon College 1500 E. Fairview Ave. Montgomery, AL 36106 (334) 833-4429 / Flowers 218B ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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] z3c.form with Boring [Re: trivial: hello world...]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim, thanks, I'm playing with a simple product called JWFind, derived from Boring now. The product sits in the products directory, can be added and removed using ZMI, it is all OK. Because I'm willing to use it in Plone, the Zope version is 2.10.6-final. Now, I'm trying to handle the view of product using form made of z3c.form. There is a problem. Currently, I'm getting Traceback (innermost last): Module ZPublisher.Publish, line 119, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 42, in call_object Module Products.JWFind.JWFind, line 55, in index_html Module z3c.form.form, line 189, in __call__ Module z3c.form.form, line 184, in update Module z3c.form.form, line 134, in update Module z3c.form.form, line 120, in updateWidgets Module zope.component._api, line 103, in getMultiAdapter Module zope.component._api, line 103, in getMultiAdapter ComponentLookupError: ((Products.JWFind.Person.Person object at 0xb5003b2c, HTTPRequest, URL=http://localhost:8091/pokus/index_html, JWFind at /pokus), InterfaceClass z3c.form.interfaces.IWidgets, u'') I guess, the error tells, that something implementing ``IWidgets`` cannot be found. But, I have no idea, how to deal with it. Maybe, should I prepare the specific layer and skin to be able to use z3cforms and If so, how to do it and especially how to register it properly? Or is there a problem with the form definition itself? Or should I register something to zope in addition to registration made in __init__? The relevant part of product source JWFind.py: def index_html(self, REQUEST=None): JWFind Form out = Person(self, REQUEST)() return out.PersonView The form is in separate file Person.py: from zope import interface, schema from z3c.form import form, field, button from plone.app.z3cform.layout import wrap_form class IPerson(interface.Interface): age = schema.Int( title=uAge, required=True) class Person(form.Form): fields = field.Fields(IPerson) ignoreContext = True # don't use context to get widget data label = uPlease enter your age @button.buttonAndHandler(u'Apply') def handleApply(self, action): data, errors = self.extractData() print data['age'] # ... or do stuff PersonView = wrap_form(Person) The whole source is attached. Please, any ideas? Thanks a lot.. David Tim Nash napsal(a): If you want simple: 1. download this product and put it into your products directory. http://www.zope.org/Members/gtk/Boring 2. Start Zope and go to 127.0.0.1:8080/manage and add the Boring product. Click test, there is your url. 3. Modify the 'Boring' code and repeat. -Tim On Tue, Mar 10, 2009 at 3:06 PM, David Zejda d...@atlas.cz wrote: Thanks for a tips, I have looked on the Guide you suggested. I think I understand the concepts, but still missing something. To make the simplest case, 1. I started with fresh instance prepared by the paster, 2. created this source: # src/my.py class Contact(object): blah blah firstName = c = Contact() 3. to the sys.path in bin/instance added the /path/to/src (which contains my.py), 4. started instance and checked, that the /path/to/src is on loaded sys.path, 5. pointed browser to localhost:8091/c/firstName . Resource c not found, Zope says. Yes, it can't be SO simple, but please, what should I do? Thanks for your patience.. David Lennart Regebro napsal(a): On Sat, Mar 7, 2009 at 23:21, David Zejda d...@atlas.cz wrote: And now, please, what to do now, to have a few python lines somewhere in the egg dir, which the zope would know how to deal with? The egg dir as you call it is a Python module, and you put Python code there. Zope knows how to deal with it, that is not the problem. What you need to do is get the Python code to deal with Zope. :) And on what url will be the hello world available then? That is completely up to you. :) The question now, is this Zope 3 or Zope 2? For Zope 3, you should probably get a book. http://worldcookery.com/ There was another book to in the beginning of Zope 3, but I don't know it has been updated. You could also, for Zope 3, opt to use Grok, which is a framework built on Zope 3 that makes Zope 3 easier: http://grok.zope.org/ For Zope 2, you can start here: http://docs.zope.org/zope2/zdgbook/source/ Then, you should probably buy the above book too. Zope 3 technologies are getting very common in Zope 2. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknCK1IACgkQ3oCkkciamVGtDACfTe7/Nj9NBsTRPAOBkOowN6lJ 31YAnAlz37ZuBgcNylLDbIyaTQDEw9yn =uJ4o -END PGP SIGNATURE- JWFind.tar.gz Description: application/gzip ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo
Re: [Zope] trivial: hello world with filesystem based egg sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for a tips, I have looked on the Guide you suggested. I think I understand the concepts, but still missing something. To make the simplest case, 1. I started with fresh instance prepared by the paster, 2. created this source: # src/my.py class Contact(object): blah blah firstName = c = Contact() 3. to the sys.path in bin/instance added the /path/to/src (which contains my.py), 4. started instance and checked, that the /path/to/src is on loaded sys.path, 5. pointed browser to localhost:8091/c/firstName . Resource c not found, Zope says. Yes, it can't be SO simple, but please, what should I do? Thanks for your patience.. David Lennart Regebro napsal(a): On Sat, Mar 7, 2009 at 23:21, David Zejda d...@atlas.cz wrote: And now, please, what to do now, to have a few python lines somewhere in the egg dir, which the zope would know how to deal with? The egg dir as you call it is a Python module, and you put Python code there. Zope knows how to deal with it, that is not the problem. What you need to do is get the Python code to deal with Zope. :) And on what url will be the hello world available then? That is completely up to you. :) The question now, is this Zope 3 or Zope 2? For Zope 3, you should probably get a book. http://worldcookery.com/ There was another book to in the beginning of Zope 3, but I don't know it has been updated. You could also, for Zope 3, opt to use Grok, which is a framework built on Zope 3 that makes Zope 3 easier: http://grok.zope.org/ For Zope 2, you can start here: http://docs.zope.org/zope2/zdgbook/source/ Then, you should probably buy the above book too. Zope 3 technologies are getting very common in Zope 2. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm25GQACgkQ3oCkkciamVFQ0QCeOHfaWDV4dSvM+TaZKyIyNpKC JpEAn0R65e8asVaogcfaCeQF5qDoj1vb =FtXB -END PGP SIGNATURE- ___ 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] trivial: hello world with filesystem based egg sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I try to develop something in the egg way, but still missing a point. I have a nice, fresh chrooted env with python, zope, plone etc. For installation I used buildout. Zope works neatly. In the home dir of chroot there is subdir of my project with subdirs like bin (scripts buildout, instance..), eggs, fake-eggs, products, src.. and in the root of project there is buildout.cfg. I'd like to start with easiest possible piece of python code in the egg form (to be redistributable), which could be treated by zope. I started with paster -t plone and answered a few questions. It created couple of dirs in src. I put the name of newly created directory to buildout.cfg sections [buildout]/eggs, [buildout]/develop, [instance]/zcml and rerun buildout. The path_to_chroot/src/projectname seems to be listed in the Debug Information of Zope instance. And now, please, what to do now, to have a few python lines somewhere in the egg dir, which the zope would know how to deal with? And on what url will be the hello world available then? Thank you for a patience.. With regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJsvNP3oCkkciamVERAgNkAJ47T0+XeXwPTEINNHbFfIMVlWfKJgCgh6CS 7xxUW25bnAgBTpD7TeRSmno= =uENF -END PGP SIGNATURE- ___ 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 )
Re: [Zope] Zope2 + Twisted
could this be satisficed by putting an apache proxy in front of both zope and twisted? On Thu, Mar 5, 2009 at 6:17 AM, Peter Sabaini pe...@sabaini.at wrote: I'd like to run a Twisted client in Zope 2.10 (for a legacy app). How do I do that? Simply loading twisted.internet is probably not a good idea since Twisted would not work well with ZServer threads, right? One thing I tried was enabling Twisted in zope.conf but that gives me the following stacktrace (abbr): ... File /usr/local/zope/2.10/src/Zope-2.10.7- final/lib/python/ZConfig/matcher.py, line 188, in constuct s = st.datatype(s) File /usr/local/zope/2.10/src/Zope-2.10.7- final/lib/python/Zope2/Startup/datatypes.py, line 349, in __init__ raise ImportError(You do not have twisted installed.) ImportError: You do not have twisted installed. I've got Twisted on my Pythonpath though. TIA, peter. ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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-Checkins] SVN: Zope/trunk/ empty object managers were evaluating to boolean false since Hanno fully implemented IContainer, because boolean checks fall through to __len__ if __nonzero__ is not i
Log message for revision 97521: empty object managers were evaluating to boolean false since Hanno fully implemented IContainer, because boolean checks fall through to __len__ if __nonzero__ is not implemented. always evaluating to true is the backwards-compatible approach Changed: U Zope/trunk/doc/CHANGES.rst U Zope/trunk/src/OFS/ObjectManager.py U Zope/trunk/src/OFS/tests/testObjectManager.py -=- Modified: Zope/trunk/doc/CHANGES.rst === --- Zope/trunk/doc/CHANGES.rst 2009-03-05 07:49:18 UTC (rev 97520) +++ Zope/trunk/doc/CHANGES.rst 2009-03-05 07:52:06 UTC (rev 97521) @@ -32,7 +32,11 @@ newer versions of the dependencies. This kind of KGS information needs to be expressed in a different way. +Bugs Fixed +++ +- Object managers should evaluate to True in a boolean test. + 2.12.0a1 (2009-02-26) - Modified: Zope/trunk/src/OFS/ObjectManager.py === --- Zope/trunk/src/OFS/ObjectManager.py 2009-03-05 07:49:18 UTC (rev 97520) +++ Zope/trunk/src/OFS/ObjectManager.py 2009-03-05 07:52:06 UTC (rev 97521) @@ -789,6 +789,9 @@ def __len__(self): return len(self.objectIds()) +def __nonzero__(self): +return True + security.declareProtected(access_contents_information, 'get') def get(self, key, default=None): return self._getOb(key, default) Modified: Zope/trunk/src/OFS/tests/testObjectManager.py === --- Zope/trunk/src/OFS/tests/testObjectManager.py 2009-03-05 07:49:18 UTC (rev 97520) +++ Zope/trunk/src/OFS/tests/testObjectManager.py 2009-03-05 07:52:06 UTC (rev 97521) @@ -379,6 +379,10 @@ om['2'] = si2 self.failUnless(len(om) == 2) +def test_nonzero(self): +om = self._makeOne() +self.failUnless(om) + def test_get(self): om = self._makeOne() si1 = SimpleItem('1') ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope] writing repozo messaging output to a file....
Actuall, std-- redirection does.. mostly. C:echo this is a test test.txt C:type test.txt this is a test C:\echo testing 2 test.txt 21 C:\type test.txt this is a test testing 2 On Thu, Feb 5, 2009 at 12:00 PM, michael.mi...@gmail.com wrote: Hi / Thanks for this. We're on Windows so unix commands won't work... On 2/5/09, Thierry Florac thierry.flo...@onf.fr wrote: Le jeudi 05 février 2009 à 07:45 -0800, Stephan Richter a écrit : On Thursday 05 February 2009, michael nt milne wrote: Ran the task and nothing was written to any of the files? Just specify an absolute path then. You do not have to create the file; it is created for you. Mmh, maybe the output is written stderr, in which case this would not work, but I am pretty sure that unix shell has an answer for that too; just read up on it. If messages are written to stderr instead of stdout, then you should do : repozo.py [your params] /var/log/repozo.log 21 to have all outputs into specified file. If you only want to log errors, then : repozo.py [your params]2 /var/log/repozo.log With hope this helps, Thierry Florac -- Chef de projet intranet/internet Office National des Forêts - Département Informatique 2, Avenue de Saint-Mandé 75570 PARIS Cedex 12 Mél : thierry.flo...@onf.fr Tél. : +33 01.40.19.59.64 Fax. : +33 01.40.19.59.85 ___ 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 ) -- michael ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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-Checkins] SVN: Zope/trunk/ specify icon size in manage_main listings so the table doesn't jump around while the icons load
Log message for revision 94922: specify icon size in manage_main listings so the table doesn't jump around while the icons load Changed: U Zope/trunk/doc/CHANGES.txt U Zope/trunk/lib/python/OFS/dtml/main.dtml -=- Modified: Zope/trunk/doc/CHANGES.txt === --- Zope/trunk/doc/CHANGES.txt 2009-01-22 04:50:33 UTC (rev 94921) +++ Zope/trunk/doc/CHANGES.txt 2009-01-22 05:12:46 UTC (rev 94922) @@ -237,6 +237,9 @@ Bugs Fixed + - Specified height/width of icons in ZMI listings so the table doesn't +jump around while loading. + - Acquisition wrappers now correctly proxy __iter__. - Launchpad #174705: ensure that the error info object exposed to a Modified: Zope/trunk/lib/python/OFS/dtml/main.dtml === --- Zope/trunk/lib/python/OFS/dtml/main.dtml2009-01-22 04:50:33 UTC (rev 94921) +++ Zope/trunk/lib/python/OFS/dtml/main.dtml2009-01-22 05:12:46 UTC (rev 94922) @@ -133,7 +133,7 @@ a href=dtml.url_quote-sequence-key;/manage_workspace dtml-in om_icons mapping img src=dtml-BASEPATH1;/dtml.url_quote-path; alt=dtml.missing-alt; - title=dtml.missing-title; border=0 //dtml-in/a + title=dtml.missing-title; border=0 width=16 height=16//dtml-in/a dtml-else dtml-if icon ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Visita mi perfil de Facebook
Hola zope-dev, Me he creado un perfil en Facebook donde puedo publicar mis fotos, vídeos, eventos, etc y quiero añadirte como amigo para que tú también puedas verlos. ¡Pero antes tienes que unirte a Facebook!. Una vez que lo hayas hecho, también podrás crear tu propio perfil. Gracias, David Para registrarte en Facebook, sigue este enlace: http://www.facebook.com/p.php?i=523449322k=551XY4PRT54M5BEBPKZXYSr ___ 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-Annce] Localizer 1.2.3 released
Localizer is a Zope product for developers and web masters. Localizer solves the problem of building multilingual products and web sites, ranging from internationalization and localization of the user interface to management of multilingual content. What is new? - Compatibility fixes for Zope 2.10/2.11 (bug #381) - Other minor fixes (including bug #304) Resources - Download http://download.hforge.org/localizer/Localizer-1.2.3.tar.gz http://download.hforge.org/itools/itools-0.20.6.tar.gz Home http://www.localizer.org/ Mailing list http://www.hforge.org/community http://archives.hforge.org/index.cgi?list=localizer Bug Tracker http://bugs.hforge.org/ -- J. David Ibáñez Itaapy http://www.itaapy.com Tel +33 (0)1 42 23 67 45 9 rue Darwin, 75018 Paris Fax +33 (0)1 53 28 27 88 ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/ follow-up to r92860...unrestrictedTraverse also needs to acquisition-wrap implicit acquirers found via adaptation (fixing regression from merge of phili
Log message for revision 92919: follow-up to r92860...unrestrictedTraverse also needs to acquisition-wrap implicit acquirers found via adaptation (fixing regression from merge of philikon-aq branch) Changed: U Zope/trunk/lib/python/OFS/Traversable.py U Zope/trunk/lib/python/OFS/tests/testTraverse.py -=- Modified: Zope/trunk/lib/python/OFS/Traversable.py === --- Zope/trunk/lib/python/OFS/Traversable.py2008-11-13 23:44:57 UTC (rev 92918) +++ Zope/trunk/lib/python/OFS/Traversable.py2008-11-14 08:22:19 UTC (rev 92919) @@ -263,6 +263,8 @@ Interface, name) if next is not None: +if IAcquirer.providedBy(next): +next = next.__of__(obj) if restricted and not validate(obj, obj, name, next): raise Unauthorized(name) elif bobo_traverse is not None: Modified: Zope/trunk/lib/python/OFS/tests/testTraverse.py === --- Zope/trunk/lib/python/OFS/tests/testTraverse.py 2008-11-13 23:44:57 UTC (rev 92918) +++ Zope/trunk/lib/python/OFS/tests/testTraverse.py 2008-11-14 08:22:19 UTC (rev 92919) @@ -397,6 +397,7 @@ self.failUnless( self.folder1.unrestrictedTraverse('+something') is 'plus') + import os, sys if __name__ == '__main__': execfile(os.path.join(sys.path[0], 'framework.py')) @@ -468,6 +469,13 @@ ... name=raise-keyerror ... permission=zope2.Public ... / + ... !-- an item that can be traversed to via adaptation -- + ... browser:page + ... for=* + ... class=Products.Five.tests.testing.fancycontent.FancyContent + ... name=acquirer + ... permission=zope2.Public + ... / ... /configure''' zcml.load_string(configure_zcml) @@ -526,7 +534,14 @@ ... 'an_attribute').index_html({}) 'an_attribute' +If we traverse to something via an adapter lookup and it provides IAcquirer, +it should get acquisition-wrapped so we can acquire attributes implicitly: + + acquirer = self.folder.unrestrictedTraverse('acquirer') + acquirer.fancy + FancyContent ... + Clean up: from zope.app.testing.placelesssetup import tearDown ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [ZWeb] svn server broken
Sorry, svn.zope.org experienced a hardware failure earlier in the day which we believed we had remediated, but which has re-surfaced as something more serious. We're working on getting it resolved and should have it back up soon, hopefully before noon EST. --Dave On Nov 10, 2008, at 2:36 AM, Martijn Faassen wrote: Hi there, Before noticing svn.zope.org was down, I noticed that buildouts seem to be failing/hanging somewhere in httplib. I now suspect this is possibly because various setup.py's have a 'url' entry that references svn.zope.org and setuptools might go off and try to read it, resulting in a hang of the buildout process. If it's possible to make http://svn.zope.org do a clear sorry, i'm not here instead of the current behavior where the browser is spinning when you try to access it, that might help. If this is too distracting currently, please ignore this message - I'm not even sure whether this fixes my issues. Regards, Martijn ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web Systems Administrator Zope Corp. 540-361-1722 [EMAIL PROTECTED] ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
[ZWeb] Instance problems
We got a page on cache problems relating to the zope.org site earlier this morning, I spent some time investigating and initially suspected a badly behaved spider from 61.230.26.210 was just slamming the servers and making them unhappy, so I dropped that IP at the firewall, but the problem has continued for the most part, and I'm not familiar enough with the ZO software to diagnose it further. At the moment, one instance is up and serving relatively well, the other three, everything on app2.zope.org and instance2 on app1.zope.org are hung on connections. I have found this error in the logs a few times, but honestly have no idea what it's refering to: 2008-10-01T06:54:31 PROBLEM(100) AutoLance AutoLance memchecker died Traceback (innermost last): File /home/zope/zope.org/var/app1/Products/AutoLance/__init__.py, line 269, in run File /home/zope/zope.org/var/app1/Products/AutoLance/linuxproc.py, line 190, in self_statm File /home/zope/zope.org/var/app1/Products/AutoLance/linuxproc.py, line 253, in get_dict TypeError: unsubscriptable object Sorry I couldn't be more helpful, if there's anything we can do, let us know, I'll probably be unavailable, but Jim knows where to find a Zope Corp SA. --Dave Systems Administrator Zope Corp. 540-361-1722 [EMAIL PROTECTED] ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
[Zope] concerns with nfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since I have started using vmware ESX as a hosting platform for zope, I've been mostly happy. However, I am wondering if I should have any concerns with storing the zodb on nfs. All our file systems on ESX are nfs mounted and lately we have had some interesting issues with the LAN that nfs runs on. So I'm am wondering if I should be concerned about storing the zodb on nfs mounted filesystems. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFI4lSfcjLlygO2EbARAne3AJ9qQg6SZQ9yMQOKnPu38Yg6B/NbggCggnVi 5P0tQ/wxNg7wBZBhAyiuVKQ= =SD8c -END PGP SIGNATURE- ___ 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 )
Re: [Zope] script calling template
Thanks to both Paul and AJ -- both suggestions were helpful. The extended description Paul gave me below was particularly use. Here's what I learned: 1) the form object is automagically handed to the template when you do a 'return context.mytemplate(item='something') 2) I assumed that I would have to pass the form object to the template -- but this is not needed. More usefull is that when 'item' is given to the template as parameter, shown above, that the template gets a NEW? namespace called 'options'. I think this is new to me. 3) then, within the template the tales expression options/item gives me 'something'. This really helps me understand better how script and templates work together. A year from now, I'll need to relearn this again and may google my answer above... Thanks to all on the plone list. On 9/10/08, Paul Winkler [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 07:57:29PM -0700, David Bear wrote: I have a script that calls a template. The template has a tal expressions like this p tal:content=structure here/ploneDoc/getText /p I want my script to call the template in such a way that the string 'ploneDoc' is replaced by a different string. I'm not sure how to go about parameterizing a tales expressions like this. It is possible, by sticking a question mark in front of ploneDoc; but afaict you can only use a variable already in the namespace, i.e. you'd have to define it first. Like so: p tal:define=docname options/ploneDoc tal:content=structure here/?docname/getText /p But I have literally never seen this obscure feature in real use, because nobody seems to know about it (I had forgotten it myself), and because it's not necessary. I'd prefer to have the script just pass in the object you want, as per this document: http://plope.com/Books/2_7Edition/BasicScripting.stx#1-3 So, in your script, something like: doc = context.restrictedTraverse(some_path) return context.mytemplate(mydoc=doc) Then, in your template just do: p tal:content=structure options/mydoc/getText/p -- Paul Winkler http://www.slinkp.com ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 )
Re: [Zope] TAL conditional expression
many thanks. I suppose I did not understand that a request.form object is given all objects 'requested' even if they are a macro in a template that is called by another template, or a fill-slot that is satisfied by another template. On 9/5/08, Andreas Jung [EMAIL PROTECTED] wrote: --On 5. September 2008 13:05:23 -0700 David Bear [EMAIL PROTECTED] wrote: I would like to test the value of a field entered on a form in a zpt, but I'm don't know the syntax basically I would like to do something like this div tal:condition=request/form/fieldA=1 do this p metal:use-macro=here/atemplate/macros/may / /div but this doesn't seem to want to work. See http://www.plope.com/Books/2_7Edition/AdvZPT.stx#2-19 Also, I would like to be able to use the same request object in both my template and the macro, but my macro doesn's seem to have access to the same request object. This statement is likely wrong since the 'request' is always available - and of course there is only 'request' object over the lifetime of a HTTP request. -aj -aj ___ 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 ) -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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] TAL conditional expression
I would like to test the value of a field entered on a form in a zpt, but I'm don't know the syntax basically I would like to do something like this div tal:condition=request/form/fieldA=1 do this p metal:use-macro=here/atemplate/macros/may / /div but this doesn't seem to want to work. Also, I would like to be able to use the same request object in both my template and the macro, but my macro doesn's seem to have access to the same request object. -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 )
Re: [Zope-dev] Dependencies and future of zope 3
Hi Martin. The concern is building high volume applications using z3, the memory footprint for virtual hosting, and the unnecessary code that adds to burden of managing security. **I only want the code I use**. I agree that the current situation does not stop folks from getting things done but overall z3 as a development platform is looking not so attractive for these reasons. It is analogous to packing two suitcases of clothes for a trip and finding you just needed a change of underwear and a shirt. Frankly is just getting difficult to accept the status quo anymore so hoping folks can get behind this sort of effort. I am trying to avoid the need for selective forking that Chris has found necessary to make progress with bfg. I want to continue using zope since these things are a big factor for the factors I stated. Martin Aspeli wrote: Hi David, David Pratt wrote: I am feeling increasing pressure and frustration to re-examine what I am doing. Zope has a wonderful code base but it is spread through many packages in the form of dependencies. As a result, a small app in a working z3 setup can start off at almost 50MB while the similar app on a competitive framework may be as little as 15 - 20 MB. Are you worried about disk space? Memory footprint? I guess the simple solution is well it you don't like it, use the another framework. Its not quite that simple since I am extremely fond of the CA architecture and have a strong desire to continue with it in some form or another into the future. I think what I am sensing more than anything is a need for zope to adapt a changing reality. zope.component, at least, is one of the packages that *does* work without the world. :) bfg is a relatively new framework that builds on wsgi and zope technologies but is an example of what can be achieved if you consume only what you need. True. I'd say that repoze.bfg is very much part of the Zope world, though. It's an example of what Zope (and it's splitting of things into many packages) has made possible. It is attractive in a number of respects for zope developers since it offers simplicity and development speed with a lightweight footprint. Yep. It's nice. :) I believe much of what is being accomplished in bfg could be accomplished in zope if it were tighter and we could focus on a leaner core of packages void of the large number of dependencies. Reducing unneeded dependencies would indeed be a good architectural goal. However, I'm not sure that having a few extra packages today is stopping people from getting things done. I think there are couple of options. One option would be to set about on a course of change to do something about this with the existing codebase. Another option is to create a core of leaner packages that could result in a much smaller, tighter core that can be competitive with the changing python landscape. I'm not sure that another armageddon of Zope - starting it all again in search of something better - will serve anybody or go particularly far. I don't think that's what bfg is doing; I think it's using the power of Zope 3 and the CA to selectively swap out the bits it doesn't like for new bits. I see that as Zope delivering, not Zope failing. bfg is currently taking the option of selectively forking some of the packages such as zope.catalog as repoze.catalog for example. Personally, I would like to see these changes occur in some way within zope. +1, but only where it actually makes sense. I'm not sure about repoze.catalog... but quite often, you may get a repoze.* that's just a wrapper around a zope.* package to make it easier to integrate with a particular framework (bfg). That's the way re-use normally happens, I think. Martin ___ 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] Dependencies and future of zope 3
Hi Roger. Great. I am willing to help with this. I understand the politics of change and feel there is most likely less impetus for change for those consuming packages as opposed to folks like yourself or I that use zope 3 as our framework. This is something that has to happen. The situation has gone on too long and the answer has been to exclude configuration. This is only a partial solution at best. Roger Ineichen wrote: Hi David Betreff: [Zope-dev] Dependencies and future of zope 3 Hi there. I have been developing with zope3 for about 4 years and would like to see zope continue in a healthy way into the future. The last couple of years particularly have brought significant change in how we deploy zope particularly with wsgi with or without the zodb. In addition, there is a increasing plethora of lightweight frameworks emerging to compete with mind share and feel zope is loosing ground in this respect. I am feeling increasing pressure and frustration to re-examine what I am doing. Zope has a wonderful code base but it is spread through many packages in the form of dependencies. As a result, a small app in a working z3 setup can start off at almost 50MB while the similar app on a competitive framework may be as little as 15 - 20 MB. To some extent, there is complexity in the politics of change needed since zope is largely consumed as packages by z2 (Plone). So the impetus for change may be less than favorable for those consuming packages in Plone as opposed to a developer interested in creating larger scale apps purely from zope 3 and other python packages. The key concern is dependencies. There have been efforts I realize to settle some of this over the past but in reality the volume of zope packages that comed together for a base build is 'pulling in the world' as i have heard it referred to many times. The testing setup is another major factor in this and the changes controversial over the eliminating the testing framework as a dependency of zope eggs. I guess the simple solution is well it you don't like it, use the another framework. Its not quite that simple since I am extremely fond of the CA architecture and have a strong desire to continue with it in some form or another into the future. I think what I am sensing more than anything is a need for zope to adapt a changing reality. bfg is a relatively new framework that builds on wsgi and zope technologies but is an example of what can be achieved if you consume only what you need. It is attractive in a number of respects for zope developers since it offers simplicity and development speed with a lightweight footprint. I believe much of what is being accomplished in bfg could be accomplished in zope if it were tighter and we could focus on a leaner core of packages void of the large number of dependencies. The grokcore packages can help with the simplicity development but do little for the dependency issues. I think there are couple of options. One option would be to set about on a course of change to do something about this with the existing codebase. Another option is to create a core of leaner packages that could result in a much smaller, tighter core that can be competitive with the changing python landscape. bfg is currently taking the option of selectively forking some of the packages such as zope.catalog as repoze.catalog for example. Personally, I would like to see these changes occur in some way within zope. In any case I am interested in hearing from folks about what can or ought to be done or whether there is interest in this direction. Many thanks. +1 I fully agree. I put the dependency cleanup on my task list and started the last couple days with reviewing the zope core packages. I think everybody whould be happy if we provide less dependencies. But if it comes to move things arround we really have a lot of work with convince everybody. It whould really help if we could build a team of developers which volunteer to review such cleanup work. That makes it easier to make decisions and avoids that people get stocked with their cleanup work. Is someone willing to help doing that task? Regards Roger Ineichen Regards David ___ 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] Dependencies and future of zope 3
Roger, you make excellent sense here. The other issue of course is the testing setup. So there is potential to operate here on a few levels to achieve something that makes much better sense for moving forward. Roger Ineichen wrote: I think the cleanup isn't really needed for zope packages itself. It's more a question how other can reuse small parts of our component architecture without to load everything. My personal meaning is, we already have a component architecture but we need to split it in a different way into reusable components. Such a split could probably not be done earlier because we didn't see all the usecases. But now since we have grok, repoze and z3c we have many more options to reuse other components and this makes it much clearer what we have to provide as reusable and what not. Regards Roger Ineichen -aj ___ 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] Dependencies and future of zope 3
Hey Martijn. These are good ideas. I also find myself importing a package for some interfaces which sort of sucks too and which there were perhaps a better solution for. Martijn Faassen wrote: Hi there, Roger Ineichen wrote: [snip] Is someone willing to help doing that task? I'm very interested in this topic as well, especially from the perspective of Grok of course. There are many strategies to go ahead in doing this. I'll list just one observation I've had here. One observation is that the pattern of '.browser' subpackages tends to expand the dependency structure significantly. Often you want to use non-browser functionality and don't care about the UI that ships with .browser. At the same time .browser tends to add dependencies to the overall package. Other times (such as for zope.app.form.browser) the main reusable functionality of a package is actually almost completely in the .browser sub package. It might be nicer to flatten the namespace then and move things from .browser into the main package. It might therefore make sense to review packages one by one, and see whether zope.foo.browser can be factored out into a zope.fooui package or something like that. Of course the question remains how we can get from A to B without a major breakage in backwards compatibility then. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ 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] Idea: Create SQL-Alchemy tables via interfaces
You may wish to look at z3c.dobbin, though the issue I have found in my own experimentation, is with association tables for many to many relationships which throws in a wrench into this otherwise elegant solution. There may be something to around this in future. Hermann Himmelbauer wrote: Hi, In my current SQLAlchemy / Zope-based design, I need the following: - SQLAlchemy table definitions - classes + mappers - Zope interfaces The problem with this design is that much data has to be defined twice, e.g. the datatype varchar(50) should be represented by an interface with TextLine(max_length=50). Moreover, any changes such as adding columns etc. also have to be done in the interface and the table definition. To overcome this, I just had the idea to use the interface/schema definitions for the table definition itself. Probably I'm not the first who had this idea, but I'm not aware of such an extension to interfaces. Any thoughts on this? Best Regards, Hermann ___ 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] Dependencies and future of zope 3
Hi Martijn. As a side note I have found immense value in the effort to split out the grok packages as it is has been very useful in my own development. I have been looking for you on irc to discuss this further to create a grokcore.traverser package and another package to abstract grok.Model (that depends more upon grokcore.component), grok.Container and grok.Application. This abstraction paves the way for general usage of megrok.rdb, megrok.rdb, and megrok.trails without the grok dependency and can bring the general usage of the model concept into regular z3. You would not believe how much this can reduce the volume of your package with these things. My preference is not to develop in grok, but at the same time these packages are excellent as I can selectively use them to reduce configuration and volume in my packages and not loose anything in the process so it is very much appreciated what you have done here. Martijn Faassen wrote: Benji York wrote: On Wed, Sep 3, 2008 at 8:40 AM, David Pratt [EMAIL PROTECTED] wrote: I am trying to avoid the need for selective forking that Chris has found necessary to make progress with bfg. I want to continue using zope [...] +1 Experimental forks to help determine what refactoring need to be done in the mother package are fine, but I hope that the findings of Plone, Grok, and repoze/bfg can all be folded back in. Agreed with this. We want Zope 3 packages to move forward, so I'm very glad that David took up this discussion. It's important we develop a bit of vision here, some guidelines, and a plan on how to get there step by step. Note that Grok hasn't been forking Zope 3 packages. We've built a few packages on top of Zope 3 that are now reusable with straight Zope 3 too, to wit, grokcore.component, grokcore.view and grokcore.security and soon grokcore.formlib. Grok has its own approaches of course, but one thing we spent quite a bit of time on is to be good Zope 3 citizens. Grok 0.14 will be built on top of these grokcore.*, and we took pains to make these compatible with straight Zope 3 projects as well. This means that if you want Grok-style configuration of adapters, views and utilities in your Zope 3 project or library you can use these projects. I have a few z3c packages sitting around that I hope to convert to use these once Grok 0.14 is released. These packages are already finding some uptake in Zope 2 projects as well. It's been interesting to see how the requirements to reuse bits of Grok in Zope 3 and Zope 2 have been pulling togeter to help factor these packages out. I think the only bit that you can really consider a 'fork' is grokproject itself, which is like an improved zopeproject. If someone wants to take it up, we could start factoring out a common core there as well. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ 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] Dependencies and future of zope 3
Hi Jim. Here is an idea I have that can help bring perspective and change. I propose that if we had the efforts of a few developers to work on a single reference application, and the eyes of others willing to inspect the package we could all benefit. The idea would be to make the reference application as lightweight as possible and work backwards so that we can measure change. This would be a simple wsgi application. I propose we use cluemapper since it is simple, small and would take little time. We can create the reference app with different backends so we can see effect of zodb also. The idea would be to use the reference to expose the issues, propose and make changes, and measure the impact of changes we are making. We also see how competitive we are compared to equivalent application on another framework in terms of no of app files, RAM consumption, no of packages, or other measures that would be important to developers. We can target the dependencies from the perspective of the impact it is having on something real as opposed to perceived. A second benefit is that we can use the application to educate folks on simple and lightweight zope development with wsgi. Jim Fulton wrote: Some high-level remarks: I agree with your sentiments. I too would like to see Zope 3 technology become more usable for lightweight applications. I'd like to see the existing code base evolve in that direction. Unfortunately, Zope 3 evolved as a monolithic development tree. Tendrils formed between packages that should have been independent. There was no incentive to keep things cleanly separated. I'm certain that this is fixable, but it will take a lot of work. I think this is happening slowly. Many of us have day jobs and it's hard to make this a priority. Jim On Sep 2, 2008, at 8:54 PM, David Pratt wrote: Hi there. I have been developing with zope3 for about 4 years and would like to see zope continue in a healthy way into the future. The last couple of years particularly have brought significant change in how we deploy zope particularly with wsgi with or without the zodb. In addition, there is a increasing plethora of lightweight frameworks emerging to compete with mind share and feel zope is loosing ground in this respect. I am feeling increasing pressure and frustration to re-examine what I am doing. Zope has a wonderful code base but it is spread through many packages in the form of dependencies. As a result, a small app in a working z3 setup can start off at almost 50MB while the similar app on a competitive framework may be as little as 15 - 20 MB. To some extent, there is complexity in the politics of change needed since zope is largely consumed as packages by z2 (Plone). So the impetus for change may be less than favorable for those consuming packages in Plone as opposed to a developer interested in creating larger scale apps purely from zope 3 and other python packages. The key concern is dependencies. There have been efforts I realize to settle some of this over the past but in reality the volume of zope packages that comed together for a base build is 'pulling in the world' as i have heard it referred to many times. The testing setup is another major factor in this and the changes controversial over the eliminating the testing framework as a dependency of zope eggs. I guess the simple solution is well it you don't like it, use the another framework. Its not quite that simple since I am extremely fond of the CA architecture and have a strong desire to continue with it in some form or another into the future. I think what I am sensing more than anything is a need for zope to adapt a changing reality. bfg is a relatively new framework that builds on wsgi and zope technologies but is an example of what can be achieved if you consume only what you need. It is attractive in a number of respects for zope developers since it offers simplicity and development speed with a lightweight footprint. I believe much of what is being accomplished in bfg could be accomplished in zope if it were tighter and we could focus on a leaner core of packages void of the large number of dependencies. The grokcore packages can help with the simplicity development but do little for the dependency issues. I think there are couple of options. One option would be to set about on a course of change to do something about this with the existing codebase. Another option is to create a core of leaner packages that could result in a much smaller, tighter core that can be competitive with the changing python landscape. bfg is currently taking the option of selectively forking some of the packages such as zope.catalog as repoze.catalog for example. Personally, I would like to see these changes occur in some way within zope. In any case I am interested in hearing from folks about what can or ought to be done or whether there is interest
Re: [Zope-dev] Dependencies and future of zope 3
Hey Roger. Sounds reasonable to me. Can we also discuss the potential of only including testing setup for dev eggs and removing testing as part of a release when the eggs are packaged to pypi or other repository for consumption. Besides loosing the dependency, this makes for happier folks external to zope that consume our eggs. While I personally do not like the contributor agreement, I am willing to sign to help out to work with you and others to get this settled. I am busy just like anyone else, but this stuff with the dependencies has to end now. Weve been with eggs for more than a couple years, progress has been made but it has been slow. Seriously, let's see what we can do to. The browser packages are a good place to start. Testing another. Third would be seriously examining dependencies of core again once this is done. Fourth might be tackling some of the zope.xxx zope.app.xxx relationships. Some of the stale packages in the main repository and placing them at another location if they are unmaintained might also be in order. If we want to folks to use zope we need to be friendly to wsgi with or without a zodb and show both sides of the coin - that CA + choice of backend + zope security + choice of traversal method (with publisher) == interesting, productive, mature, dynamic and efficient. On Wed, Sep 3, 2008 at 3:06 PM, Roger Ineichen [EMAIL PROTECTED] wrote: Hi Betreff: Re: [Zope-dev] Dependencies and future of zope 3 On Wed, Sep 3, 2008 at 11:41 AM, Stephan Richter [EMAIL PROTECTED] wrote: For several packages we took the following approach. Most packages that have browser packages are in zope.app; for example, zope.app.folder (we did not convert this package yet). We then took the API and moved it to zope.folder. Maybe we should create a new namespace package for browser code. How about zope.browser? Most packages which are interesting for reuse provide more or less only ZMI related views. What about zope.zmi if they provide views for the ZMI. This views are allmost unuseable outside the ZMI (know as Rotterdam skin) Regards Roger Ineichen -- Benji York Senior Software Engineer Zope Corporation ___ 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 ) ___ 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] Dependencies and future of zope 3
Roger, what you say makes good sense. I will get agreement signed and sent and off to Jim. I am much more optimistic than I have been for a long time. This stuff has really been bothering me since I am concerned about efficient wsgi virtual host deployments and zope is unnecessarily heavy. Personally I would like to see a core zope install with a footprint of no more that 20MB with just essential packages. I am a believer in zope and I am encouraged by the support for change. I also realize some of this will be disruptive but it is necessary. A wiki page will be helpful to communicate and get the best ideas for moving ahead. There are a number of good folks here that understand the circumstances so we have an excellent opportunity to act on this. On Wed, Sep 3, 2008 at 9:09 PM, Roger Ineichen [EMAIL PROTECTED] wrote: Hi David Betreff: Re: [Zope-dev] Dependencies and future of zope 3 Hey Roger. Sounds reasonable to me. Can we also discuss the potential of only including testing setup for dev eggs and removing testing as part of a release when the eggs are packaged to pypi or other repository for consumption. I guess we do not have tets eggs. What do you mean with test eggs. I think extras_require test is a pattern which let's you use the extras or not if you use an egg. By default an egg has only dependencies the defined packages in install_requires. Or are I'm wrong? Besides loosing the dependency, this makes for happier folks external to zope that consume our eggs. While I personally do not like the contributor agreement, I am willing to sign to help out to work with you and others to get this settled. I am busy just like anyone else, but this stuff with the dependencies has to end now. Weve been with eggs for more than a couple years, progress has been made but it has been slow. Seriously, let's see what we can do to. Cool any help is welcome. The browser packages are a good place to start. Testing another. Third would be seriously examining dependencies of core again once this is done. Fourth might be tackling some of the zope.xxx zope.app.xxx relationships. Some of the stale packages in the main repository and placing them at another location if they are unmaintained might also be in order. I think we should start with identify the hard core dependencies and list them in a proposal or another document in the zope wiki. Anybody can list their ideas of what should be done and list ideas how we can solve the problems. We also can use that paper for vote about the different refactorings. Such a proposal/paper could also be usefull for others which don't read each mail. We have different kind of refactorings which all solve some problems. I think we should not start with the browser views. There are some core dependencies we need to cleanup first. Right now I'm working forward with small refactorings which solve some dependencies to zope.app.form (ITerms) and zope.app.authentication (IPaswordManager). After that, my goal is to work on the testing framework, offering a clean testing (skin) layer, which should make it possible to write functional tests without to use the basic, default or rotterdam skin and the zope.app.authentication package. I guess that's what the repoze people need to have too. Your help is defently very welcome. Go ahead with the contributor agreement sing up and let Jim know that I volunteer for you. If we want to folks to use zope we need to be friendly to wsgi with or without a zodb and show both sides of the coin - that CA + choice of backend + zope security + choice of traversal method (with publisher) == interesting, productive, mature, dynamic and efficient. Sounds interesting but let's put that on the todo later list. Regards Roger Ineichen _ END OF MESSAGE On Wed, Sep 3, 2008 at 3:06 PM, Roger Ineichen [EMAIL PROTECTED] wrote: Hi Betreff: Re: [Zope-dev] Dependencies and future of zope 3 On Wed, Sep 3, 2008 at 11:41 AM, Stephan Richter [EMAIL PROTECTED] wrote: For several packages we took the following approach. Most packages that have browser packages are in zope.app; for example, zope.app.folder (we did not convert this package yet). We then took the API and moved it to zope.folder. Maybe we should create a new namespace package for browser code. How about zope.browser? Most packages which are interesting for reuse provide more or less only ZMI related views. What about zope.zmi if they provide views for the ZMI. This views are allmost unuseable outside the ZMI (know as Rotterdam skin) Regards Roger Ineichen -- Benji York Senior Software Engineer Zope Corporation ___ 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
[Zope-dev] Dependencies and future of zope 3
Hi there. I have been developing with zope3 for about 4 years and would like to see zope continue in a healthy way into the future. The last couple of years particularly have brought significant change in how we deploy zope particularly with wsgi with or without the zodb. In addition, there is a increasing plethora of lightweight frameworks emerging to compete with mind share and feel zope is loosing ground in this respect. I am feeling increasing pressure and frustration to re-examine what I am doing. Zope has a wonderful code base but it is spread through many packages in the form of dependencies. As a result, a small app in a working z3 setup can start off at almost 50MB while the similar app on a competitive framework may be as little as 15 - 20 MB. To some extent, there is complexity in the politics of change needed since zope is largely consumed as packages by z2 (Plone). So the impetus for change may be less than favorable for those consuming packages in Plone as opposed to a developer interested in creating larger scale apps purely from zope 3 and other python packages. The key concern is dependencies. There have been efforts I realize to settle some of this over the past but in reality the volume of zope packages that comed together for a base build is 'pulling in the world' as i have heard it referred to many times. The testing setup is another major factor in this and the changes controversial over the eliminating the testing framework as a dependency of zope eggs. I guess the simple solution is well it you don't like it, use the another framework. Its not quite that simple since I am extremely fond of the CA architecture and have a strong desire to continue with it in some form or another into the future. I think what I am sensing more than anything is a need for zope to adapt a changing reality. bfg is a relatively new framework that builds on wsgi and zope technologies but is an example of what can be achieved if you consume only what you need. It is attractive in a number of respects for zope developers since it offers simplicity and development speed with a lightweight footprint. I believe much of what is being accomplished in bfg could be accomplished in zope if it were tighter and we could focus on a leaner core of packages void of the large number of dependencies. The grokcore packages can help with the simplicity development but do little for the dependency issues. I think there are couple of options. One option would be to set about on a course of change to do something about this with the existing codebase. Another option is to create a core of leaner packages that could result in a much smaller, tighter core that can be competitive with the changing python landscape. bfg is currently taking the option of selectively forking some of the packages such as zope.catalog as repoze.catalog for example. Personally, I would like to see these changes occur in some way within zope. In any case I am interested in hearing from folks about what can or ought to be done or whether there is interest in this direction. Many thanks. Regards David ___ 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] pickle passing over a socket
It seems to me that it could be usefull to have a zope method for passing python pickles to external processes through a unix domain socket. My thinking was to use this as a means to abstract a data base connection. Yes, I know there are zsql methods, sqlalchemy and other products to do this. But my thought was to have a generilzed method for just passing a pickle to an external process that could do anything with it. Perhaps it could pass a pickle to a queue that would handle the pickle if the site need some high volume handling of data. Then one could have another python process listening on the socket -- ready to receive pickles for zope. Does this sound like something that could be usefull -- or is it reduntant with some other feature that zope may have for sending data to external processes? -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 )
Re: [Zope] pickle passing over a socket
On 8/22/08, Andreas Jung [EMAIL PROTECTED] wrote: --On 22. August 2008 09:33:21 -0700 David Bear [EMAIL PROTECTED] wrote: It seems to me that it could be usefull to have a zope method for passing python pickles to external processes through a unix domain socket. My thinking was to use this as a means to abstract a data base connection. Yes, I know there are zsql methods, sqlalchemy and other products to do this. But my thought was to have a generilzed method for just passing a pickle to an external process that could do anything with it. Perhaps it could pass a pickle to a queue that would handle the pickle if the site need some high volume handling of data. Ever heard of XMLRPC? Sorry, your idea sounds like a bit like broken-by-design or like I-have-never-heard--anything-of-higher-protocols. You are correct, there are higher level protocols. However, since I was only thinking of using python processes, I thought I could simplify the whole design by just passing pickles. No need to parse an xml object, use fast cpickle module. -aj -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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] products in client instances
If I have zeo and 3 clients (client1, client2, client2) its seems that it would be convenient to have the Products directory be a symlink to a master products directory. Is there any reason not to do this? Or, is there a 'super directory' where all products can be installed for all zeo clients already? -- David Bear College of Public Programs at ASU 602-464-0424 ___ 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 )
Re: [Zope-dev] Re: zope.sqlalchemy dependencies does not respect setup.py dev egg
Hi Laurence. I reverted to 0.2 and I am good to go. I will upgrade to 0.3 when dobbin can use beta0.5.3. Many thanks. Regards, David Laurence Rowe wrote: zope.sqlalchemy specifically requires a SessionExtension hook added in 0.4.7 and 0.5.0b3 to fix a bug that came to light in porting dobbin over to use it: New objects added to a session did not cause a transaction join, so were not committed at the end of the transaction unless the database was accessed. SQLAlchemy 0.4.7 or 0.5beta3 now required. Other than that nothing really changed since 0.2, you should be able to just use that. Laurence David Pratt wrote: Hi. I have been working with z3c.dobbin 0.4.1 which uses zope.sqlalchemy and z3c.saconfig. The last usable state was 4 days ago when changes were made to release of zope.sqlalchemy where dependencies were changed without changing the version. Revision 88953 was made to zope.sqlalchemy but shows the same package version as 88952 (where SA dependencies were changed to no longer include beta0.5.2). beta0.5.2 was the requirement for z3c.dobbin and it will not work with beta0.5.3. Malthe is currently making changes to dobbin in the interim so it will eventually work again. I thought by checking out revision 88952 and using it as a dev egg in my buildout, I could get back to work. Is this a bug in buildout since dev egg should take precedence regardless? I guess there were some problems with how this was handled. If trunk had been marked as 0.3dev it might have made the difference because both were 0.3 regardless of the change of state and dependencies. When I run the buildout the dev egg's requires.txt is below regardess of what is in setup.py. Doesn't matter what I do my build fails. Any suggestions? Many thanks. Regards, David requires.txt setuptools SQLAlchemy=0.4.7,!=0.5.0beta1,!=0.5.0beta2 transaction zope.interface [test] zope.testing docutils setup.py install_requires=[ 'setuptools', 'SQLAlchemy==0.5.0beta2', # or =0.5b3 'transaction', 'zope.interface', ], ___ 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 ) ___ 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] zope.sqlalchemy dependencies does not respect setup.py dev egg
Hi. I have been working with z3c.dobbin 0.4.1 which uses zope.sqlalchemy and z3c.saconfig. The last usable state was 4 days ago when changes were made to release of zope.sqlalchemy where dependencies were changed without changing the version. Revision 88953 was made to zope.sqlalchemy but shows the same package version as 88952 (where SA dependencies were changed to no longer include beta0.5.2). beta0.5.2 was the requirement for z3c.dobbin and it will not work with beta0.5.3. Malthe is currently making changes to dobbin in the interim so it will eventually work again. I thought by checking out revision 88952 and using it as a dev egg in my buildout, I could get back to work. Is this a bug in buildout since dev egg should take precedence regardless? I guess there were some problems with how this was handled. If trunk had been marked as 0.3dev it might have made the difference because both were 0.3 regardless of the change of state and dependencies. When I run the buildout the dev egg's requires.txt is below regardess of what is in setup.py. Doesn't matter what I do my build fails. Any suggestions? Many thanks. Regards, David requires.txt setuptools SQLAlchemy=0.4.7,!=0.5.0beta1,!=0.5.0beta2 transaction zope.interface [test] zope.testing docutils setup.py install_requires=[ 'setuptools', 'SQLAlchemy==0.5.0beta2', # or =0.5b3 'transaction', 'zope.interface', ], ___ 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 )