October 2005 - Zope-Dev

New(ish) Windows test failures on Zope trunk
by Tim Peters 26 Oct '05

26 Oct '05

I see two test failures today on Zope(2) trunk, WinXP, Python version doesn't matter (same thing under 2.3.5 & 2.4.2). Failure in test testRegisterTranslations (zope.app.i18n.tests.testi18ndirectives.DirectivesTest) Traceback (most recent call last): File "C:\Code\Zope\lib/python\zope\app\i18n\tests\testi18ndirectives.py", line 55, in testRegisterTranslations eq(util._catalogs, {'en': [unicode(path)]}) File "C:\python23\lib\unittest.py", line 302, in failUnlessEqual raise self.failureException, \ AssertionError: {u'en': [u'C:\\Code\\Zope\\lib\\python\\zope\\i18n\\tests\\locale\\en\\LC_MESSAGES\\zope-i18n.mo']} != {'en': [u'C:\\Code\\Zope\\lib/python\\zope\\i18n\\tests\\locale\\en\\LC_MESSAGES\\zope-i18n.mo']} One dict has a Unicode key there while the other dict doesn't, and the "python" part of the value is preceded by a backslash in one but a forward slash in the other. Then: Failure in test checkDuplicate (zope.configuration.config.ConfigurationContext) Failed doctest test for zope.configuration.config.ConfigurationContext.checkDuplicate File "C:\Code\Zope\lib/python\zope\configuration\config.py", line 259, in checkDuplicate File "C:\Code\Zope\lib/python\zope\configuration\config.py", line 281, in zope.configuration.config.ConfigurationContext .checkDuplicate Failed example: try: c.checkDuplicate(d + os.path.normpath('/bar.zcml')) except ConfigurationError, e: str(e).endswith("bar.zcml' included more than once") Expected: True Got nothing _Looks_ like the test expected ConfigurationError to be raised, but that ConfigurationError was not raised. Oddly enough, I believe this is related to the first test failure. Dumping some prints in checkDuplicate() shows that, when the test fails, `path` is 'C:\\Code\\Zope\\lib\\python\\zope\\configuration\\bar.zcml' and self._seen_files is a set with two elements: 'C:\\Code\\Zope\\lib/python\\zope\\configuration\\bar.zcml' '\\foo.zcml' As in the first test too, the character preceding the "python" part differs. The path passed is indeed not in the set of _seen_files, so ConfigurationError is indeed not raised. No idea where this slash-vs-backslash confusion ultimately comes from, though. Who recently checked code in hard-coding "/" as a path separator?

1 0

Experiencing TypeError: The object is not a PySECURITY_ATTRIBUTES object
by Chris Mattmann 25 Oct '05

25 Oct '05

Hi Folks, I¹m experiencing the following error on windows XP SP2. The error is described at: http://mail.zope.org/pipermail/zope-checkins/2005-June/029495.html I¹ve installed: Zope 2.8.3-final for windows from the zope.org site Plone-2.1.1, just the products from the plone.org site Python 2.3.5 for windows from the python.org site Before installing Plone, and having just installed Zope and Python, I can start Zope without any error. Of course, this is without any Products in my instance directory. Then, when I stop Zope, then copy the Plone products over, then try to restart Zope from my $INSTANCE_HOME/bin/runzope.bat program, I get that PySECURITY_ATTRIBUTES error. I went to the Zope folder in my Program Files directory and then went to lib/python/Signals/WinSignalHandler.py, and I notice that the patch applied to fix this bug appears to have been applied to that file, however, I¹m still getting the error. Does anybody have any clue why? Thanks so much. Cheers, Chris ______________________________________________ Chris A. Mattmann Chris.Mattmann(a)jpl.nasa.gov Staff Member Modeling and Data Management Systems Section (387) Data Management Systems and Technologies Group _________________________________________________ Jet Propulsion Laboratory Pasadena, CA Office: 171-266B Mailstop: 171-246 _______________________________________________________ Disclaimer: The opinions presented within are my own and do not reflect those of either NASA, JPL, or the California Institute of Technology.

3 4

Why is test.py silent by default
by Tres Seaver 25 Oct '05

25 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung. Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWSAW+gerLs4ltQ4RAs3NAKCodcPqXIDlTJ3QGa4z8gFNc92LcACeJNLc 7ms5+UFjYgv+i/M6/I4eIOc= =wEwp -----END PGP SIGNATURE-----

4 4

[Fwd: [Squishdot] global name 'MessageDialog' is not defined]
by Chris Withers 25 Oct '05

25 Oct '05

Hi All, Has MessageDialog gone away or has it just moved? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

Re: [z3-five] Reintegrating Zope 3 (was Re: RFC: Five 1.2 and 1.3 release plan)
by Jim Fulton 24 Oct '05

24 Oct '05

Jim Fulton wrote: > > I was about to start working on integrating the new test runner > and was reminded that we need to integrate Zope differently than we did > for 2.8/3.0. Then, we took advantage of the fact that packages not > included > in the Zope X3 3.0 release were trimmed from the corresponding branch. > This didn't happen for 3.1 and isn't going to happen moving forward. > > For starters, I'm going to give Zope 2 it's own zope directory. > (I'm also going to use the pkgutil mechanism: > > file:///home/jim/Documentation/Python-Docs-2.3.3/lib/module-pkgutil.html > > which was added for us. :) > > Then I'm going to use externals to get the packages we use, > initially from whatever tag z2 is using now. OK, this is done. Unfortunately, because svn:externals is half baked, you'll need to remove your existing zope package before updating an existing sandbox. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

1 0

Re: SVN: Zope/branches/zodb-blobs-branch/ Move to ZODB 3.6.0b1.
by Tres Seaver 24 Oct '05

24 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Peters wrote: > Log message for revision 39583: > Move to ZODB 3.6.0b1. > > ZopeDatabase.createDB(): Plug database_name into config rather than > passing it to ZODBDatabase.open(). More should be done to detect > conflicting <zodb_db> section name and database_name, but I'm not > sure where all the relevant code is. > > There are a number of DeprecationWarnings about subtransactions when > running the tests. Should be repaired. > > One test failure, but doesn't look like it's related to ZODB: Nope. This one can be remediated by merging the fix on the current Five trunk: $ svn merge -r18808:18809 svn://codespeak.net/svn/z3/Five/trunk/ . Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDXTaC+gerLs4ltQ4RAqCsAJwNHqtn52MD6LI9b0XEbSK6g43jJQCfWP3w 2hHGKap4apmHmfi3XKWXd6o= =drIS -----END PGP SIGNATURE-----

2 1

Re: [Zope-CMF] Better DeprecationWarnings (was Re: SVN: CMF/trunk/CMFDefault/Portal.py - reverted Portal.py change of r39125 to fix BBB temporarily)
by Tres Seaver 21 Oct '05

21 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote: > Tres Seaver wrote: > >> Note that I have just figured out that we can make DeprecationWarnings >> more useful by passing the 'stacklevel' argument to 'warnings.warn'; >> passing a value of 2 for that argument causes the warning to be reported >> against the *caller* of the code issuing the warning, which makes it >> possible to find and remove the deprecated use. > > > Oooh, coool. Reckon it'd be a good idea if I changed all the deprecation > warnings in Zope to do the same? +10. > I've always found them totally useless 'cos they don't tell you where > they come from and so you can't fix them... > > Bit like the random ZODB errors when it no longer has the class for some > long-forgotten object burried deep in an opaque pickled data structure > which you have no hope of ever finding and deleting... but I digress ;-) Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDV7I2+gerLs4ltQ4RAiTPAJ9ARNJ9C33+BrFMfD7bIgoMNSryQACgtGc5 nzgXeHE9NTZ79BQ5dF9rkN8= =B+U3 -----END PGP SIGNATURE-----

3 3

RestrictedPython, TALES Expressions and CMF
by Sidnei da Silva 19 Oct '05

19 Oct '05

(sorry for the cross-post) I'm currently facing an issue that seems to be a result of a bad interaction between CMF, TALES and Restricted Python. The issue currently happens when: 1. A TALES 'Path Expression' in 'Caching Policy Manager' is evaluated 2. The result of evaluating a sub-expression is a Python Script (eg: object/modified where 'modified' is a Python Script) 3. The context as built by CMF doesn't define 'here' What happens in this case is that the call will end up in PageTemplates/ZRPythonExpr.py:call_with_ns, which is reproduced here for your pleasure: def call_with_ns(f, ns, arg=1): td = Rtd() td.this = ns['here'] td._push(ns['request']) td._push(InstanceDict(td.this, td)) td._push(ns) try: if arg==2: return f(None, td) else: return f(td) finally: td._pop(3) Now, given that there has been a decision of deprecating 'here' in favor of 'context', I'm not exactly sure about the fix. CMF seems to create expression contexts in two places off the top of my head: In 'CMFCore/Expression.py' and 'CMFCore/CachingPolicyManager.py'. None of those define 'here' or 'context' but instead just 'object'. In 'Products/PageTemplates/TALES.py', in the 'translate' function, 'here' is also hardcoded, but that should be less of an issue as code reaching into that function *should* have a proper expression context. The question then is, which code is wrong? PageTemplates for relying on 'here' being defined, or CMF for not defining 'here'? I volunteer to provide a fix with tests as soon as someone clarifies which one needs to be fixed. As a reminder, 'actions' as defined by 'portal_actions' tool and anything that derives from 'ActionProviderBase' suffer from the same issue. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com

3 5

Five status on Zope trunk (was Re: [Zope-dev] Mountpoints)
by Tim Peters 18 Oct '05

18 Oct '05

[Tim] >> I'm copying Fred because he may remember more about this than I do. >> Fred, do you know of a reason why I can't stitch a newer ZODB into >> Zope(2) trunk? I have a dim, fading memory of the last attempt >> failing, and of agreeing in email to wait for the "5 guys" to "do >> something" before trying again. Sorry for not being more specific ... [Fred] > We need to do the zpkg/ZODB switch all at once because it affects how > extensions get their include files. Aha! That vaguely rings another vague bell ;-) The ZODB 3.5+ source code spells "#include" in its C files in a different way, and that can't work with the way Zope trunk is currently built. > When I tried switching the Zope 2 trunk before, there was a problem due > to Five tests failing. I don't remember the details, but the Five-folks > seemed to think things would be better with newer versions of Five. > > Since Five development is done elsewhere, though, it's hard to tell what the > deal is with that. Can anyone working on Five comment here, please? I gather that the first 2.9 beta release occurs in 2 weeks, and if Fred can't do his zpkgtools work, I can't update the trunk to a newer ZODB, and then Chris McDonough can't do his rework of mount points (the original topic of this thread), and then (best case) the world economy collapses. > I snapshotted what I did get done as the zpkg-build-branch, so we can get > back to it without duplicating work. So there's no reason yet to be depressed ;-)

2 1

svn.zope.org borked?
by Andreas Jung 18 Oct '05

18 Oct '05

Hi, all changes I made for the last hotfix release (patch for the reST .. include problem) have disappeared from the SVN (both from 2.8 branch and the trunk). I am *pretty sure* that I commited all changes. Is there something broken with the SVN database? Andreas

2 2