- Zope-Dev - Zope lists

Re: [Zope-dev] Re: z3 server+publication refactor for z2
by Lennart Regebro 18 Apr '06

18 Apr '06

FYI there was a couple of hours work done on this today at the sprint in Paris. It seemed to us the the next necessary step in Sidneis branch was to make Zope2 traversal adapters for non-zope3 objects. This work has now started, in the form of refactoring the BaseRequest traversal into Zope3 type traversal chunks that we can make adapters of. Current problem: getRole is called with the entry_name unless the subobject was gotten via a getitem interface, when it's called with None. As we want to do the getRole part outside of the name traversal, we don't know in which way the name was gotten. So we need to solve that tomorrow somehow. You can check the current status work at http://svn.zope.org/Zope/branches/easter-sprint_traversal-refactor/

1 0

Is there a function to get the object type?
by Takahashi, Michael 18 Apr '06

18 Apr '06

Hi guys, I'm trying to write a function that checks to see if the current object is a 'Folder'. I am using this tutorial as a reference: http://plone.org/documentation/how-to/pre-populated-folder To create a new content object, the following command is used: parent.invokeFactory(id=id, type_name='Folder') Is there a function that can check what type this newly created object is? Obviously its 'Folder' in this example, but I'd like to be able to get the type_name of an object returned anywhere in my site to see if it is a 'Folder'. Thanks, Mike

5 4

z3 server+publication refactor for z2
by Florent Guillaume 13 Apr '06

13 Apr '06

Hi, Sidnei has been working on the Zope 2 publication-refactor branch where he's allowed the use of the Zope 3 Twisted-based server, and of a Zope 3 based publication process. I'd like to see this merge branched in Zope 2 trunk because I'd like Zope 2.10 to be Twisted-based. What's missing from the branch preventing this? What problems have been encountered? (This query is a reaction to my diving in to current asyncore+medusa +ThreadedAsync+PubCore that gives me nightmares when I realize I'll have to implement new server types or new stuff more akin to the ZEO storage server.) Thanks, Florent PS: what do people think of changing ZEO so that it integrates with Twisted properly instead of relying on a private event loop hack [please move to zodb-dev if you answer this] -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

6 12

RE: [Zope-dev] Is there a function to get the object type?
by Takahashi, Michael 10 Apr '06

10 Apr '06

Thank you to everyone who helped. I've found the answer. In my case, the key was to use 'isPrincipiaFolderish' So to run a check to see if something is a folder: if context.isPrincipiaFolderish: print "It's a folder!" else: print "Nope, it's not a folder." Mike -----Original Message----- From: zope-dev-bounces+mtakahashi=oid.ucla.edu(a)zope.org [mailto:zope-dev-bounces+mtakahashi=oid.ucla.edu@zope.org] On Behalf Of Paul Winkler Sent: Monday, April 10, 2006 4:43 PM To: zope-dev(a)zope.org Subject: Re: [Zope-dev] Is there a function to get the object type? On Mon, Apr 10, 2006 at 03:46:41PM -0700, Takahashi, Michael wrote: > Hi guys, > > I'm trying to write a function that checks to see if the current object > is a 'Folder'. > > I am using this tutorial as a reference: > > http://plone.org/documentation/how-to/pre-populated-folder > > To create a new content object, the following command is used: > > parent.invokeFactory(id=id, type_name='Folder') > > Is there a function that can check what type this newly created object > is? Obviously its 'Folder' in this example, but I'd like to be able to > get the type_name of an object returned anywhere in my site to see if it > is a 'Folder'. This is really a CMF question and belongs on the zope-cmf mailing list; invokeFactory() is a method of CMFCore.PortalFolder. But to answer your question: someobject.portal_type -PW -- Paul Winkler http://www.slinkp.com _______________________________________________ Zope-Dev maillist - Zope-Dev(a)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 )

1 0

RE: [Zope-dev] Is there a function to get the object type?
by Takahashi, Michael 10 Apr '06

10 Apr '06

Thanks Aruna, That returns all portal_types. However I would like to see what the current type of an object is. For example, if I am currently here: /mysite/index.html I would like to know that the current object is a 'Document' And if I were here: /mysite/folder I would like to know that the current object is a 'Folder' Thanks, Mike ________________________________ From: Aruna Kathiria [mailto:aruna@cignex.com] Sent: Monday, April 10, 2006 3:58 PM To: Takahashi, Michael; zope-dev(a)zope.org Subject: RE: [Zope-dev] Is there a function to get the object type? Hello: You can get the types from following function. Once you get the list of the types of the object type, you can use it as you want. ptypes = context.portal_types.objectValues() sample script to test is: ------------------------------- ptypes = context.portal_types.objectValues() for ptype in ptypes: print ptype return printed ------------------------------ With Regards, Aruna Kathiriya Sr.Consultant, CIGNEX Technologies, Inc T: 408.327.9900 x 306 F: 408.273.6785 E: aruna(a)cignex.com U: www.cignex.com "Implement IT Right" ________________________________ From: zope-dev-bounces(a)zope.org [mailto:zope-dev-bounces@zope.org] On Behalf Of Takahashi, Michael Sent: Monday, April 10, 2006 3:47 PM To: zope-dev(a)zope.org Subject: [Zope-dev] Is there a function to get the object type? Hi guys, I'm trying to write a function that checks to see if the current object is a 'Folder'. I am using this tutorial as a reference: http://plone.org/documentation/how-to/pre-populated-folder To create a new content object, the following command is used: parent.invokeFactory(id=id, type_name='Folder') Is there a function that can check what type this newly created object is? Obviously its 'Folder' in this example, but I'd like to be able to get the type_name of an object returned anywhere in my site to see if it is a 'Folder'. Thanks, Mike

1 0

RE: [Zope-dev] Is there a function to get the object type?
by Aruna Kathiria 10 Apr '06

10 Apr '06

Hello: You can get the types from following function. Once you get the list of the types of the object type, you can use it as you want. ptypes = context.portal_types.objectValues() sample script to test is: ------------------------------- ptypes = context.portal_types.objectValues() for ptype in ptypes: print ptype return printed ------------------------------ With Regards, Aruna Kathiriya Sr.Consultant, CIGNEX Technologies, Inc T: 408.327.9900 x 306 F: 408.273.6785 E: aruna(a)cignex.com U: www.cignex.com "Implement IT Right" ________________________________ From: zope-dev-bounces(a)zope.org [mailto:zope-dev-bounces@zope.org] On Behalf Of Takahashi, Michael Sent: Monday, April 10, 2006 3:47 PM To: zope-dev(a)zope.org Subject: [Zope-dev] Is there a function to get the object type? Hi guys, I'm trying to write a function that checks to see if the current object is a 'Folder'. I am using this tutorial as a reference: http://plone.org/documentation/how-to/pre-populated-folder To create a new content object, the following command is used: parent.invokeFactory(id=id, type_name='Folder') Is there a function that can check what type this newly created object is? Obviously its 'Folder' in this example, but I'd like to be able to get the type_name of an object returned anywhere in my site to see if it is a 'Folder'. Thanks, Mike

1 0

Re: [Zope-DB] Bug in ZSQL method result caching?
by Chris Withers 10 Apr '06

10 Apr '06

Hi Dirk, I'm CC'ing in zope-dev as more people there may care... Dirk Datzert wrote: > Hi Chris, > > you wrote on the ZOPE-DB mailing-list > http://www.mail-archive.com/zope-db@zope.org/msg00417.html at Fri, 24 > Feb 2006 09:15:31 -0800. > > I have seen this KeyError after updating from Zope 2.7.5 to Zope 2.8.6 > last weekend about every 20 Minutes. > > Have you ever got a fix about this ? Nope, never got a fix... > I fixed it like this: > > =========================================== > > if len(cache) > max_cache / 2: > keys=tcache.keys() > keys.reverse() > while keys and (len(keys) > max_cache or keys[-1] < t): > key=keys[-1] > q=tcache[key] > del tcache[key] > - if int(cache[q][0]) == key: > + if cache.has_key(q) and int(cache[q][0]) == key: > del cache[q] > del keys[-1] > > =========================================== > > Maybe this is worth to do a bug entry on zope.org ? Definitely. Would you mind adding one? Is it possible to write tests for this code? If not, would anyone mind if I applied this patch to the 2.8 and 2.9 branches along with the trunk? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

bug in trunk ZopePageTemplate.py?
by Paul Winkler 07 Apr '06

07 Apr '06

Running CMF 2.0-beta tests against the zope 2 trunk, I noticed a test failure that's not happening under zope 2.9: Error in test testHTML (Products.CMFDefault.tests.test_Document.DocumentFTPGetTests) Traceback (most recent call last): File "/usr/lib/python2.4/unittest.py", line 260, in run testMethod() File "/home/pw/Downloads/Apps/Net/z2-trunk/Products/CMFDefault/tests/test_Document.py", line 391, in testHTML ZopePageTemplate('source_html') ) File "/home/pw/Downloads/Apps/Net/z2-trunk/lib/python/Products/PageTemplates/ZopePageTemplate.py", line 135, in __init__ self.pt_edit(text, content_type, encoding) File "/home/pw/Downloads/Apps/Net/z2-trunk/lib/python/Products/PageTemplates/ZopePageTemplate.py", line 143, in pt_edit text = text.strip() AttributeError: 'NoneType' object has no attribute 'strip' This is because the semantics of ZopePageTemplate(id, text=None) have changed. It used to be that if text was None, the contents of www/default.html would be used. That no longer happends, and pt_edit can't accept None for the text. Was this intentional or is it a bug? -- Paul Winkler http://www.slinkp.com

2 2

Re: [Checkins] SVN: Zope/trunk/ Fixed collector 2057: Testing.makequest broke getPhysicalPath()
by Stefan H. Holek 07 Apr '06

07 Apr '06

For the record: I am still opposed to this change. It basically endows the request (as in self.REQUEST) with a getPhysicalPath method, and I have no idea what kind of side-effects this may have. AFAICS your test suite is the only suite around that wants to request- wrap non-root objects. There's nothing wrong with using your own makerequest for your own test suite, if this is what you want. But I don't think your use-case warrants changing Zope. Stefan On 5. Apr 2006, at 22:51, Paul Winkler wrote: > Log message for revision 66581: > Fixed collector 2057: Testing.makequest broke getPhysicalPath() > when used on anything other than an app object. > Also added an 'environ' argument if you want to use something > other than os.environ, and added a couple trivial tweaks from > ZopeTestCase.makereqeust. > Added unit tests for this stuff. > > > > Changed: > U Zope/trunk/doc/CHANGES.txt > U Zope/trunk/lib/python/Testing/makerequest.py > A Zope/trunk/lib/python/Testing/tests/ > A Zope/trunk/lib/python/Testing/tests/__init__.py > A Zope/trunk/lib/python/Testing/tests/test_makerequest.py > > -=- > Modified: Zope/trunk/doc/CHANGES.txt > =================================================================== > --- Zope/trunk/doc/CHANGES.txt 2006-04-05 20:04:59 UTC (rev 66580) > +++ Zope/trunk/doc/CHANGES.txt 2006-04-05 20:51:21 UTC (rev 66581) > @@ -46,6 +46,9 @@ > > Features added > > + - Testing.makerequest: Added an 'environ' argument so > + clients can use mappings other than os.environ. > + > - Updated to Docutils 0.4.0 > > - reStructuredText: The default value for the 'stylesheet' > @@ -202,6 +205,10 @@ > > Bugs Fixed > > + - Collector #2057: Allow Testing.makerequest to work with > + any acquisition-supporting root object, not just Zope2.app. > + Formerly, if you did that, getPhysicalPath() was broken. > + > - Collector #2051: Applied patch by Yoshinori Okuji to fix some > XML export/import problems, including tests for that feature. > > > Modified: Zope/trunk/lib/python/Testing/makerequest.py > =================================================================== > --- Zope/trunk/lib/python/Testing/makerequest.py 2006-04-05 > 20:04:59 UTC (rev 66580) > +++ Zope/trunk/lib/python/Testing/makerequest.py 2006-04-05 > 20:51:21 UTC (rev 66581) > @@ -19,27 +19,50 @@ > import makerequest > app = makerequest.makerequest(Zope2.app()) > > +You can optionally pass stdout to be used by the response, > +and an environ mapping to be used in the request. > +Defaults are sys.stdout and os.environ. > + > +If you don't want to start a zope app in your test, you can wrap > other > +objects, but they must support acquisition and you should only wrap > +your root object. > + > + > $Id$ > > """ > > import os > -from os import environ > from sys import stdin, stdout > from ZPublisher.HTTPRequest import HTTPRequest > from ZPublisher.HTTPResponse import HTTPResponse > from ZPublisher.BaseRequest import RequestContainer > > -def makerequest(app, stdout=stdout): > +def makerequest(app, stdout=stdout, environ=None): > resp = HTTPResponse(stdout=stdout) > - environ['SERVER_NAME']='foo' > - environ['SERVER_PORT']='80' > - environ['REQUEST_METHOD'] = 'GET' > + if environ is None: > + environ = os.environ > + environ.setdefault('SERVER_NAME', 'foo') > + environ.setdefault('SERVER_PORT', '80') > + environ.setdefault('REQUEST_METHOD', 'GET') > req = HTTPRequest(stdin, environ, resp) > - > + req._steps = ['noobject'] # Fake a published object. > + req['ACTUAL_URL'] = req.get('URL') # Zope 2.7.4 > + > # set Zope3-style default skin so that the request is usable for > - # Zope3-style view look-ups > + # Zope3-style view look-ups. > from zope.app.publication.browser import setDefaultSkin > setDefaultSkin(req) > > - return app.__of__(RequestContainer(REQUEST = req)) > + requestcontainer = RequestContainer(REQUEST = req) > + # Workaround for collector 2057: ensure that we don't break > + # getPhysicalPath if app has that method. > + # We could instead fix Traversable.getPhysicalPath() to check for > + # existence of p.getPhysicalPath before calling it; but it's such > + # a commonly called method that I don't want to impact > performance > + # for something that AFAICT only affects makerequest() in > + # practice. > + if getattr(app, 'getPhysicalPath', None) is not None: > + requestcontainer.getPhysicalPath = lambda: () > + > + return app.__of__(requestcontainer) > > Added: Zope/trunk/lib/python/Testing/tests/__init__.py > =================================================================== > --- Zope/trunk/lib/python/Testing/tests/__init__.py 2006-04-05 > 20:04:59 UTC (rev 66580) > +++ Zope/trunk/lib/python/Testing/tests/__init__.py 2006-04-05 > 20:51:21 UTC (rev 66581) > @@ -0,0 +1 @@ > +# > > > Property changes on: Zope/trunk/lib/python/Testing/tests/__init__.py > ___________________________________________________________________ > Name: svn:keywords > + "Author Date Revision" > > Added: Zope/trunk/lib/python/Testing/tests/test_makerequest.py > =================================================================== > --- Zope/trunk/lib/python/Testing/tests/test_makerequest.py > 2006-04-05 20:04:59 UTC (rev 66580) > +++ Zope/trunk/lib/python/Testing/tests/test_makerequest.py > 2006-04-05 20:51:21 UTC (rev 66581) > @@ -0,0 +1,65 @@ > +##################################################################### > ######### > +# > +# Copyright (c) 2006 Zope Corporation and Contributors. All Rights > Reserved. > +# > +# This software is subject to the provisions of the Zope Public > License, > +# Version 2.1 (ZPL). A copy of the ZPL should accompany this > distribution. > +# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR > IMPLIED > +# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE > IMPLIED > +# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND > FITNESS > +# FOR A PARTICULAR PURPOSE. > +# > +##################################################################### > ######### > +"""Unit tests of makequest. > + > +$Id$ > +""" > + > +import unittest > + > +from Acquisition import Implicit > +from Testing.makerequest import makerequest > +from OFS.SimpleItem import SimpleItem > + > +class MakerequestTests(unittest.TestCase): > + > + def test_makerequest(self): > + # The argument must support acquisition. > + self.assertRaises(AttributeError, makerequest, object()) > + # After the call, it will have a REQUEST attribute. > + item = Implicit() > + self.failIf(hasattr(item, 'REQUEST')) > + item = makerequest(item) > + self.failUnless(hasattr(item, 'REQUEST')) > + > + def test_dont_break_getPhysicalPath(self): > + # see http://www.zope.org/Collectors/Zope/2057 > + item = SimpleItem() > + self.assertEqual(item.getPhysicalPath(), ('',)) > + self.assertEqual(item.getPhysicalPath(), > + makerequest(item).getPhysicalPath()) > + > + def test_stdout(self): > + # You can pass a stdout arg and it's used by the response. > + import cStringIO > + out = cStringIO.StringIO() > + item = makerequest(SimpleItem(), stdout=out) > + item.REQUEST.RESPONSE.write('aaa') > + out.seek(0) > + written = out.read() > + self.failUnless(written.startswith('Status: 200 OK\n')) > + self.failUnless(written.endswith('\naaa')) > + > + def test_environ(self): > + # You can pass an environ argument to use in the request. > + environ = {'foofoo': 'barbar'} > + item = makerequest(SimpleItem(), environ=environ) > + self.assertEqual(item.REQUEST.environ['foofoo'], 'barbar') > + > +def test_suite(): > + suite = unittest.TestSuite() > + suite.addTest(unittest.makeSuite(MakerequestTests)) > + return suite > + > +if __name__=='__main__': > + unittest.TextTestRunner().run(test_suite()) > > > Property changes on: Zope/trunk/lib/python/Testing/tests/ > test_makerequest.py > ___________________________________________________________________ > Name: svn:keywords > + "Author Date Revision" > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins -- Anything that happens, happens. --Douglas Adams

4 5

Zope Test Summaries 2006-04-05
by Stefan H. Holek 07 Apr '06

07 Apr '06

[We seem to have lost Steve Alexander's test summarizer. I will contact him in a separate mail.] The switch to Python 2.3.4 caused tests for Zope 2.7 and 2.8 to experience a funny problem with the logging module. Anybody want to take a guess what's up here? I know these are not a truly "supported" configurations, but still. http://mail.zope.org/pipermail/zope-tests/2006-April/004645.html http://mail.zope.org/pipermail/zope-tests/2006-April/004647.html The VHM tests in Zope 2.9 and trunk broke last night: http://mail.zope.org/pipermail/zope-tests/2006-April/004648.html http://mail.zope.org/pipermail/zope-tests/2006-April/004649.html Stefan -- Anything that happens, happens. --Douglas Adams

4 7