- Zope-Dev - Zope lists

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 29 Oct '05

29 Oct '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '<unknown>': <no reason specified> Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 29 Oct '05

29 Oct '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '<unknown>': <no reason specified> Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 29 Oct '05

29 Oct '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Re: [Zope-dev] Experiencing TypeError: The object is not a PySECURITY_ATTRIBUTES object
by Tim Peters 27 Oct '05

27 Oct '05

[Mark Hammond] > FYI, there is a new pywin32 build out now that should solve this problem > without requiring any imports to be reordered. Yay! > It would be great if whoever turns the crank for the next Zope/Windows > builds (which may even turn out to be me! :) uses build 205. Andreas Jung made a "surprise" release of Zope 2.8.4 today, but only the tarball, not a Windows installer. If you want to make the latter, more than fine by me, else I'll try to make one tomorrow (with your build 205, of course -- will require some retroactive patching of the 2.8.4 tag no matter who does it). > Sadly, I believe it is not trivial to install a new pywin32 build into a > Zope binary. You could patch it up though by opening the pywin32 release > executable in WinZip (or similar), then replacing 'pywintypes.py' and > extracting a new "_win32sysloader.pyd" module. Ya, like Windows users are gonna do _that_ <wink>. > Finally, I believe another way to solve this problem would be to remove > pywintypes23.dll from the system32 directory (the the underlying problem is > that 2 copies of this DLL are being loaded into memory). However, doing > this may prevent other things (such as your existing Python installation) > from working correctly, so do this with caution. Zope does not install > anything into system32, so presumably something else on your system is also > using Python. All "recent" PySECURITY_ATTRIBUTES complaints I know about have come from people using both Zope and Plone. I don't know anything about Plone installation, but it's natural to suspect that Plone is the source of the other pywin32 installation, and possibly of compounding sys.path convolutions too. So, a natural question based on this ignorance: is it enough for just Zope to install build 205, if Plone also installs its own (older) pywin32 and mangles sys.path so that its pywin32 is also visible? I suspect (but don't know) that's what's happening. It would be a lot better if a Plone user tested the proposed solution before we release another Windows Zope that may still turn out not to solve Plone's problems here.

3 4

RE: [Zope-dev] Experiencing TypeError: The object is not a PySECURITY_ATTRIBUTES object
by Chris Mattmann 27 Oct '05

27 Oct '05

Hi Mark, Success! That fixed the problem. Thanks for the excellent help. I'd say this patch is a good for the next iteration of builds ;) Take care, 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. > -----Original Message----- > From: Mark Hammond [mailto:mhammond@skippinet.com.au] > Sent: Wednesday, October 26, 2005 4:00 PM > To: Chris Mattmann > Subject: RE: [Zope-dev] Experiencing TypeError: The object is not a > PySECURITY_ATTRIBUTES object > > Hi Chris, > You could try the solution with the attached files: > > pywintypes.py replaces an existing file in what I believe is the > "{zope}\bin\lib\site-packages\win32\lib directory. Please take a copy of > the original in case I totally screw you :) > > _win32sysloader.pyd is a new file, and goes into the existing directory > "{zope}\bin\lib\site-packages\win32", where you should find many other > .pyd > files. > > Simply restart Zope after this, and the problems should vanish. > > Mark. > > > -----Original Message----- > > From: Chris Mattmann [mailto:chris.mattmann@jpl.nasa.gov] > > Sent: Thursday, 27 October 2005 8:18 AM > > To: Tim Peters; Mark Hammond > > Cc: zope-dev(a)zope.org > > Subject: Re: [Zope-dev] Experiencing TypeError: The object is not a > > PySECURITY_ATTRIBUTES object > > > > > > Hi Guys, > > > > Thanks for your responses. I'll investigate the version of Plone > > that I had > > downloaded (2.1.1) to see whether or not there are any calls to the > > pywintypes32 library within the Plone products that could be causing > this > > problem. I had suspected it may be a Plone issue because I didn't see > the > > problem when I just installed Zope, and started it up. Only after > > adding the > > Plone products did I start to see the problem. However, I wasn't sure > what > > might be causing it because I'm not really a Python guy. To be > > honest, I've > > never used it before. So I'll check into this and get back to you. I'd > be > > happy to test the proposed solution BTW, if you send me a tarball, and > > report the results to the list. > > > > Thanks! > > > > Cheers, > > Chris > > > > > > > > On 10/26/05 3:00 PM, "Tim Peters" <tim.peters(a)gmail.com> wrote: > > > > > [Mark Hammond] > > >> FYI, there is a new pywin32 build out now that should solve > > this problem > > >> without requiring any imports to be reordered. > > > > > > Yay! > > > > > >> It would be great if whoever turns the crank for the next > Zope/Windows > > >> builds (which may even turn out to be me! :) uses build 205. > > > > > > Andreas Jung made a "surprise" release of Zope 2.8.4 today, but only > > > the tarball, not a Windows installer. If you want to make the latter, > > > more than fine by me, else I'll try to make one tomorrow (with your > > > build 205, of course -- will require some retroactive patching of the > > > 2.8.4 tag no matter who does it). > > > > > >> Sadly, I believe it is not trivial to install a new pywin32 > > build into a > > >> Zope binary. You could patch it up though by opening the > > pywin32 release > > >> executable in WinZip (or similar), then replacing 'pywintypes.py' and > > >> extracting a new "_win32sysloader.pyd" module. > > > > > > Ya, like Windows users are gonna do _that_ <wink>. > > > > > >> Finally, I believe another way to solve this problem would be to > remove > > >> pywintypes23.dll from the system32 directory (the the > > underlying problem is > > >> that 2 copies of this DLL are being loaded into memory). > > However, doing > > >> this may prevent other things (such as your existing Python > > installation) > > >> from working correctly, so do this with caution. Zope does not > install > > >> anything into system32, so presumably something else on your > > system is also > > >> using Python. > > > > > > All "recent" PySECURITY_ATTRIBUTES complaints I know about have come > > > from people using both Zope and Plone. I don't know anything about > > > Plone installation, but it's natural to suspect that Plone is the > > > source of the other pywin32 installation, and possibly of compounding > > > sys.path convolutions too. > > > > > > So, a natural question based on this ignorance: is it enough for just > > > Zope to install build 205, if Plone also installs its own (older) > > > pywin32 and mangles sys.path so that its pywin32 is also visible? I > > > suspect (but don't know) that's what's happening. It would be a lot > > > better if a Plone user tested the proposed solution before we release > > > another Windows Zope that may still turn out not to solve Plone's > > > problems here. > > > > ______________________________________________ > > 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. > > > > > > > > > >

1 0

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