Re: [Zope-dev] Python 2.7 and the ZTK - three test failures
On 2010-7-5 23:08, Hanno Schlichting wrote: Hi there, with Python 2.7 final being released, I ran the ZTK tests against it. zope.exceptions, zope.formlib and zope.proxy all have one test output related failure. We seem to have a lot of problems with doctests breaking due to changes in exception formatting. Perhaps a policy to check exceptions using a try/except or self.assertRaises instead of relying on exact formatting would be useful? Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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 summit topics
On 07/05/2010 08:56 PM, Sidnei da Silva wrote: On Mon, Jul 5, 2010 at 3:52 PM, Martijn Faassenfaas...@startifact.com wrote: (But hurry.resource is not perfect; I think it'd be better to step out of Python land and create a Javascript packaging system somewhat modeled on Python's, with easy integration into Python projects. A sprint task?) YUI 3's loader comes to mind (as its the one I have most experience with). I've used YUI 2's loader (and hurry.resource was inspired by it). I don't know YUI 3's loader so I should take a look at it. (It strikes me that whatever its technical merits, a javascript packaging system will have to appear neutral politically and YUI's loader won't do that. The YUI 3 loader is connected to the YUI global object?) Anyway, YUI's loader only solves part of the problem - at least the YUI 2 loader doesn't feature a packaging system, just a loading system. I want the ease of saying: my project depends on YUI version blah and having YUI version blah being there, just like I can do for a Python package. Such a package should include a dependency map of the included resources as well, not just the code. Regards, Martijn ___ 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 summit topics
On 07/05/2010 09:32 PM, Jim Fulton wrote: On Mon, Jul 5, 2010 at 2:56 PM, Sidnei da Silva sidnei.da.si...@canonical.com wrote: On Mon, Jul 5, 2010 at 3:52 PM, Martijn Faassenfaas...@startifact.com wrote: (But hurry.resource is not perfect; I think it'd be better to step out of Python land and create a Javascript packaging system somewhat modeled on Python's, with easy integration into Python projects. A sprint task?) YUI 3's loader comes to mind (as its the one I have most experience with). Ditto for dojo. :) All javascript libraries grow their own packaging systems... I'd be nice if they were all compatible with a more neutral version. Some consolidation would be nice, plus bridging all of that to the Python packaging world. I'd envision a JSON-based metadata system that include intra and inter package dependencies between resources, a way to wrap these packages, a package host along the lines of PyPI, and integration with the Python packaging system. And then wrap all these javascript libraries up and upload them to the package index. The wrapping up can be fairly straightforward (YUI contains a dependency graph), or need analysis. Regards, Martijn ___ 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] Python 2.7 and the ZTK - three test failures
On 07/06/2010 09:46 AM, Wichert Akkerman wrote: On 2010-7-5 23:08, Hanno Schlichting wrote: Hi there, with Python 2.7 final being released, I ran the ZTK tests against it. zope.exceptions, zope.formlib and zope.proxy all have one test output related failure. We seem to have a lot of problems with doctests breaking due to changes in exception formatting. Perhaps a policy to check exceptions using a try/except or self.assertRaises instead of relying on exact formatting would be useful? I wish the Python developers saw the exception messages as a core part of their interface, but I guess they won't. While I acknowledge its fragility, I do like the way doctests express exceptions quite a lot, so I'd prefer something that kept them like that. We've used normalization in the past, so if core Python exception messages changed I'd imagine more normalization could help again? Anyway, since we've only had a few test failures the problems with changing message formatting seems to be limited, right? Regards, Martijn ___ 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] Python 2.7 and the ZTK - three test failures
Am 06.07.2010, 12:23 Uhr, schrieb Martijn Faassen faas...@startifact.com: While I acknowledge its fragility, I do like the way doctests express exceptions quite a lot, so I'd prefer something that kept them like that. We've used normalization in the past, so if core Python exception messages changed I'd imagine more normalization could help again? Anyway, since we've only had a few test failures the problems with changing message formatting seems to be limited, right? I think this has come up before especially in reference to Lennart's port to Python 3.x. Any test that depends upon exception formatting is likely to be a problem. In the specific zope.formlib test we have a doctest embedded within another: MyForm(None, request)() # doctest: +NORMALIZE_WHITESPACE +ELLIPSIS There were errors: (u'Invalid floating point data', exceptions.ValueError instance at ...) I think this is bound to cause problems sooner or later in any environment. The test here is whether, and not how, the constraint is fulfilled and the nature of the exception is irrelevant. The more common u'Invalid floating point data' in browser.contents would be a better solution, I think. Furthermore, while it's great that form.txt actually runs I wasn't aware that it contained any additional tests that are not already run and I've always treated it as testable documentation not as an integral part of the formlib tests. But I'm ready to be believe this is a large misconception on my part. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] Python 2.7 and the ZTK - three test failures
Hey, On 07/06/2010 01:04 PM, Charlie Clark wrote: In the specific zope.formlib test we have a doctest embedded within another: MyForm(None, request)() # doctest: +NORMALIZE_WHITESPACE +ELLIPSIS There were errors: (u'Invalid floating point data', exceptions.ValueError instance at ...) What do you mean, a doctest embedded within another? I'm probably missing something. Furthermore, while it's great that form.txt actually runs I wasn't aware that it contained any additional tests that are not already run and I've always treated it as testable documentation not as an integral part of the formlib tests. But I'm ready to be believe this is a large misconception on my part. I follow the principle that all testable stuff should actually be run during the tests - just in case. :) Regards, Martijn ___ 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] Python 2.7 and the ZTK - three test failures
Am 06.07.2010, 13:12 Uhr, schrieb Martijn Faassen faas...@startifact.com: What do you mean, a doctest embedded within another? I'm probably missing something. No, it's probably me getting the explicit doctest call wrong. It looks to my novice eyes like print statement is being passed to a doctest method. In matters like these it's usually safe to assume I'm wrong! :-) Proposed solution: rewrite this particular doctest to use a test browser. Furthermore, while it's great that form.txt actually runs I wasn't aware that it contained any additional tests that are not already run and I've always treated it as testable documentation not as an integral part of the formlib tests. But I'm ready to be believe this is a large misconception on my part. I follow the principle that all testable stuff should actually be run during the tests - just in case. hm, I don't think that can be argued with really, particularly given the amount of time I've actually studied this and other documents over reading the code. But I do think that, whether the module runs as specified, and whether the documentation is up to snuff, are of a different nature and, consequently, so are their failures. Shouldn't we be testing documentation differently? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] Python 2.7 and the ZTK - three test failures
On 07/06/2010 01:27 PM, Charlie Clark wrote: Am 06.07.2010, 13:12 Uhr, schrieb Martijn Faassenfaas...@startifact.com: What do you mean, a doctest embedded within another? I'm probably missing something. No, it's probably me getting the explicit doctest call wrong. It looks to my novice eyes like print statement is being passed to a doctest method. In matters like these it's usually safe to assume I'm wrong! :-) No, that comment (if you mean that?) is just a way to send configuration parameters to the doctest engine. It calls the view. hm, I don't think that can be argued with really, particularly given the amount of time I've actually studied this and other documents over reading the code. But I do think that, whether the module runs as specified, and whether the documentation is up to snuff, are of a different nature and, consequently, so are their failures. Shouldn't we be testing documentation differently? I think a failure in documentation should ideally show up when running the tests. I do agree that documentation and tests have different concerns and that mixing them can (but does not necessarily have to) lead to poor documentation. Regards, Martijn ___ 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 Tests: 26 OK, 10 Failed, 5 Unknown
Summary of messages to the zope-tests list. Period Mon Jul 5 12:00:00 2010 UTC to Tue Jul 6 12:00:00 2010 UTC. There were 41 messages: 6 from Zope Tests, 3 from buildbot at enfoldsystems.com, 11 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 1 from ct at gocept.com, 9 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED: Repository policy check found errors in 417 projects From: ct at gocept.com Date: Mon Jul 5 21:13:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016113.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:12:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016123.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:24:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016124.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:34:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016125.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:46:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016126.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:53:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016127.html Subject: FAILED : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:01:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016128.html Subject: FAILED : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:08:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016129.html Subject: FAILED : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:15:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016130.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 6 07:29:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016151.html Unknown --- Subject: UNKNOWN : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:32:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016118.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:34:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016119.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.4-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:00:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016142.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.5-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016143.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:03:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016144.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Jul 5 16:54:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016111.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Jul 5 16:54:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016112.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 5 21:24:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016114.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 5 21:26:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016115.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:28:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016116.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:30:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016117.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon Jul 5 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016120.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon Jul 5 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016122.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon Jul 5 22:00:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016121.html Subject: OK : winbot /
[Zope-dev] 1.4.4 bugfix release for zc.catalog
Hi, Grok would be greatly helped with a 1.4.4 bugfix release of zc.catalog. The fix we want is already implemented, we just need a release. Is someone willing to do that? (or, would allow me to do it by granting pypi right for the package? My pypi username is jw). kind regards, jw ___ 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 Toolkit - 1.0a1 release
On 6/30/10 21:47 PM, Hanno Schlichting wrote: To use the ZTK release, you can use: [buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg This first release focuses on getting something out and defining the actual technical outcome of a release. Currently the release outcome is tailored to the needs of the three frameworks. Grok's groktoolkit now extends from this 1.0a1 release. After today's zc.catlog bugfix release, Grok is using the ZTK now without any issues. Thanks Hanno! regards, jw ___ 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 Tests: 26 OK, 10 Failed, 5 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:12:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016123.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:24:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016124.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:34:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016125.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:46:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016126.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 22:53:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016127.html Subject: FAILED : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:01:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016128.html Subject: FAILED : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:08:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016129.html Subject: FAILED : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Mon Jul 5 23:15:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016130.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 6 07:29:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016151.html The can't remove an open file problem on Windows shows up in all of these failures. I know I saw at least one or two others in there somewhere, but they also only fail on Windows, which means I can't diagnose directly. Unknown --- Subject: UNKNOWN : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:32:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016118.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 5 21:34:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016119.html These are build failures in the mr.developer step to get DataTime checked out. We should figure out how to fix that, but in the meantime, why are we not running with a released version of DateTime? Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.4-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:00:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016142.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.5-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:00:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016143.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 6 02:03:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016144.html Thanks to Enfold for running the ZODB tests, which are failing to build due to a missing bootstrap.py in the ZODB trunk; I just checked one in. ALso, Alan, can you please change the subject line such that the summarizer can interpret success / failure? The spec is here: http://docs.zope.org/zopetoolkit/process/buildbots.html#informing-the-zope-developer-community-about-build-results Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwzQMoACgkQ+gerLs4ltQ6l3wCeNt7lPsABMrm3lOn3SCHpPKmR lBwAn1cd9xkuQb4moZJYEKCdfPL01lqq =SIXr -END PGP 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 )
Re: [Zope-dev] Zope Toolkit - 1.0a1 release
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting ha...@hannosch.eu wrote: On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. I've yet to hear any response to my post about non-backward-compatible classes: https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? -Fred -- Fred L. Drake, Jr.fdrake at gmail.com A storm broke loose in my mind. --Albert Einstein ___ 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 Toolkit - 1.0a1 release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Drake wrote:
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting ha...@hannosch.eu wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm
happy to announce the first 1.0 alpha release of the Zope Toolkit.
I've yet to hear any response to my post about non-backward-compatible
classes:
https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html
Is no one else concerned about the backward incompatibility introduced
by zope.pluggableauth.plugins.session.SessionCredentialsPlugin?
Given that ZODB3 and zope.app.container are still non-optional
dependencies of the package, I can't see any reason not to restore those
base classes.
Note that I dont use zope.{,app.}pluggableauthservice, and so have no
skin in that particular game.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwzRPYACgkQ+gerLs4ltQ5G6QCghXIGoYcM9cyEISQ2vE+sbxK/
q58An28jL5EGrWytF3C4pi6zSM3Xu8O8
=beIj
-END PGP 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 )
Re: [Zope-dev] Zope Tests: 26 OK, 10 Failed, 5 Unknown
Hello, Tuesday, July 6, 2010, 4:42:23 PM, you wrote: TS ALso, Alan, can you please change the subject line such that the TS summarizer can interpret success / failure? The spec is here: TS http://docs.zope.org/zopetoolkit/process/buildbots.html#informing-the-zope-developer-community-about-build-results And here is a working buildbot config to copy: http://buildbot.afpy.org/ztk1.0/master.cfg -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: You couldn't even prove the White House staff sane beyond a reasonable doubt. - Ed Meese, on the Hinckley verdict ___ 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 Toolkit - 1.0a1 release
On 07/06/2010 05:00 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichtingha...@hannosch.eu wrote: On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. I've yet to hear any response to my post about non-backward-compatible classes: https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes. zope.pluggableauth doesn't seem to depend on zope.app.container? Or did you mean zope.container? I think you meant the latter. I have no objection to adding these back in (zope.container.contained.Contained, that is), as it doesn't change the dependency. Regards, Martijn ___ 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 Toolkit - 1.0a1 release
On Tue, Jul 6, 2010 at 4:54 PM, Fred Drake fdr...@acm.org wrote: I've yet to hear any response to my post about non-backward-compatible classes: https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? Apparently not :) But your proposal sounded good to me. Just go ahead. Hanno ___ 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] Invitation to bug day in July
On 06/28/2010 06:33 PM, Christian Theune wrote: Hi everyone, our bug day in July needs scheduling and we'd like you to tell us which day works best for you if you want to participate: http://doodle.com/akd2f59kdadp86r2 Ok, so although Charlie indicated that his doodle is wrong, I'll take that as an indicator that Wednesday is generally more acceptable. So, next Wednesday (2010-07-14) is the next bug day. Here's a wiki page so you can also register there to indicate participation: http://wiki.zope.org/ztk/BugDay20100714 So, again: Everyone can participate in a bug day: whether you want to report a bug, discuss a bug or a feature, fix bugs or do anything else to improve Zope software, feel free to step by on #z...@freenode and join us! Hope to see you next week! Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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 Toolkit - 1.0a1 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: On 07/06/2010 05:00 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichtingha...@hannosch.eu wrote: On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. I've yet to hear any response to my post about non-backward-compatible classes: https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes. zope.pluggableauth doesn't seem to depend on zope.app.container? Or did you mean zope.container? I think you meant the latter. I have no objection to adding these back in (zope.container.contained.Contained, that is), as it doesn't change the dependency. Fred was commenting on a change to zope.app.authentication, actually, which has dependencies on ZODB3 and zope.app.container. Sorry for any confusion. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwzWOAACgkQ+gerLs4ltQ4vgQCgt5Qnb3qBdKMqxJYGcG34o4Kv 6eMAoN0u3ZqCoeET0Jg5iclZMXbgoVG8 =MmRq -END PGP 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 )
Re: [Zope-dev] Invitation to bug day in July
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/6/10 17:53 , Christian Theune wrote: So, next Wednesday (2010-07-14) is the next bug day. Here's a wiki page so you can also register there to indicate participation: http://wiki.zope.org/ztk/BugDay20100714 I'll not that the simple table you chose is impossibly finicky to follow and add data to. I fiddled for 5 minutes to find the right magic number of spaces between my column entries to not make the whole table _disappear_. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwzYPAACgkQRAx5nvEhZLLCaQCfToM2NP8NvicIgkCmM/BSvRRF CqsAnjFRJfWkUr5tZQ75K4OW7O+kTwtG =UhnW -END PGP 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 )
Re: [Zope-dev] Python 2.7 and the ZTK - three test failures
Hi again.
On Mon, Jul 5, 2010 at 11:08 PM, Hanno Schlichting ha...@hannosch.eu wrote:
with Python 2.7 final being released, I ran the ZTK tests against it.
zope.exceptions, zope.formlib and zope.proxy all have one test output
related failure.
I fixed all of those and released new versions. bin/test-ztk should
now pass under Python 2.7.
RestrictedPython will need a security review.
I hear David Glick has started to look into this. Applause!
Running bin/test-zopeapp still gives failures in two packages:
zope.app.publisher and zope.app.wsgi.
I'm not familiar enough with that code to fix any of those.
Hanno
Full test output:
Running test-zopeapp-zope.app.publisher
test-zopeapp-zope.app.publisher failed with:
Running zope.app.publisher.testing.AppPublisherLayer tests:
Set up zope.app.publisher.testing.AppPublisherLayer in 1.360 seconds.
Failure in test
/opt/eggs/zope.app.publisher-3.10.1-py2.7.egg/zope/app/publisher/xmlrpc/tests/../README.txt
Traceback (most recent call last):
File /opt/python/parts/opt/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File /opt/python/parts/opt/lib/python2.7/doctest.py, line 2153, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for README.txt
File
/opt/eggs/zope.app.publisher-3.10.1-py2.7.egg/zope/app/publisher/xmlrpc/tests/../README.txt,
line 0
--
File
/opt/eggs/zope.app.publisher-3.10.1-py2.7.egg/zope/app/publisher/xmlrpc/tests/../README.txt,
line 65, in README.txt
Failed example:
proxy.contents()
Exception raised:
Traceback (most recent call last):
File /opt/python/parts/opt/lib/python2.7/doctest.py, line 1248, in __run
compileflags, 1) in test.globs
File doctest README.txt[7], line 1, in module
proxy.contents()
File /opt/python/parts/opt/lib/python2.7/xmlrpclib.py, line
1224, in __call__
return self.__send(self.__name, args)
File /opt/python/parts/opt/lib/python2.7/xmlrpclib.py, line
1570, in __request
verbose=self.__verbose
File
/opt/eggs/zope.app.testing-3.7.5-py2.7.egg/zope/app/testing/xmlrpc.py,
line 62, in request
return self._parse_response(
AttributeError: ZopeTestTransport instance has no attribute
'_parse_response'
[... snip lots more failures with the same problem ...]
Ran 1 tests with 1 failures and 0 errors in 0.163 seconds.
Running zope.testing.testrunner.layer.UnitTests tests:
Tear down zope.app.publisher.testing.AppPublisherLayer in 0.001 seconds.
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Ran 11 tests with 0 failures and 0 errors in 0.089 seconds.
Tearing down left over layers:
Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Total: 12 tests, 1 failures, 0 errors in 1.791 seconds.
Running test-zopeapp-zope.app.wsgi
test-zopeapp-zope.app.wsgi failed with:
Running zope.app.wsgi.BrowserLayer tests:
Set up zope.app.wsgi.BrowserLayer in 0.222 seconds.
Failure in test test_file_returns (zope.app.wsgi.tests)
Failed doctest test for zope.app.wsgi.tests.test_file_returns
File /opt/eggs/zope.app.wsgi-3.9.2-py2.7.egg/zope/app/wsgi/tests.py,
line 61, in test_file_returns
--
File /opt/eggs/zope.app.wsgi-3.9.2-py2.7.egg/zope/app/wsgi/tests.py,
line 77, in zope.app.wsgi.tests.test_file_returns
Failed example:
browser.open('http://localhost/@@test-file-view.html')
Exception raised:
Traceback (most recent call last):
File
/opt/eggs/zope.testing-3.9.4-py2.7.egg/zope/testing/doctest/__init__.py,
line 1355, in __run
compileflags, 1) in test.globs
File doctest zope.app.wsgi.tests.test_file_returns[line 16,
example 6], line 1, in module
browser.open('http://localhost/@@test-file-view.html')
File
/opt/eggs/zope.testbrowser-3.9.0-py2.7.egg/zope/testbrowser/browser.py,
line 237, in open
self.mech_browser.open(url, data)
File /opt/eggs/mechanize-0.2.1-py2.7.egg/mechanize/_mechanize.py,
line 204, in open
return self._mech_open(url, data, timeout=timeout)
File /opt/eggs/mechanize-0.2.1-py2.7.egg/mechanize/_mechanize.py,
line 231, in _mech_open
response = UserAgentBase.open(self, request, data)
File /opt/eggs/mechanize-0.2.1-py2.7.egg/mechanize/_opener.py,
line 193, in open
response = urlopen(self, req, data)
File /opt/eggs/mechanize-0.2.1-py2.7.egg/mechanize/_urllib2_fork.py,
line 344, in _open
'_open', req)
File /opt/eggs/mechanize-0.2.1-py2.7.egg/mechanize/_urllib2_fork.py,
line 332, in _call_chain
result = func(*args)
File
/opt/eggs/wsgi_intercept-0.4-py2.7.egg/wsgi_intercept/urllib2_intercept/wsgi_urllib2.py,
line 34, in http_open
return self.do_open(WSGI_HTTPConnection, req)
File /opt/python/parts/opt/lib/python2.7/urllib2.py, line
1142, in do_open
Re: [Zope-dev] Zope Tests: 26 OK, 10 Failed, 5 Unknown
On Tue, Jul 6, 2010 at 1:58 PM, Zope Tests Summarizer
zope-te...@epy.co.at wrote:
Summary of messages to the zope-tests list.
Period Mon Jul 5 12:00:00 2010 UTC to Tue Jul 6 12:00:00 2010 UTC.
There were 41 messages: 6 from Zope Tests, 3 from buildbot at
enfoldsystems.com, 11 from buildbot at winbot.zope.org, 11 from ccomb at
free.fr, 1 from ct at gocept.com, 9 from jdriessen at thehealthagency.com.
Test failures
-
Subject: FAILED : winbot / ztk_dev py_265_win64
From: buildbot at winbot.zope.org
Date: Mon Jul 5 22:46:05 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016126.html
One of the test failures is this:
Running test-zopeapp-zope.app.applicationcontrol
test-zopeapp-zope.app.applicationcontrol failed with:
Running zope.app.applicationcontrol.testing.ApplicationControlLayer tests:
Set up zope.app.applicationcontrol.testing.ApplicationControlLayer
in 1.843 seconds.
Ran 4 tests with 0 failures and 0 errors in 0.516 seconds.
Running zope.testing.testrunner.layer.UnitTests tests:
Tear down zope.app.applicationcontrol.testing.ApplicationControlLayer
in 0.000 seconds.
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
'svn' is not recognized as an internal or external command,
operable program or batch file.
Failure in test test_WrongLocale
(zope.app.applicationcontrol.tests.test_zopeversion.Test)
Traceback (most recent call last):
File c:\Python26_32\lib\unittest.py, line 279, in run
testMethod()
File
c:\buildslave\ztk_dev_py_265_win32\build\src\zope.app.applicationcontrol\src\zope\app\applicationcontrol\tests\test_zopeversion.py,
line 136, in test_WrongLocale
self.assert_(zv.result.startswith('Development/Revision: '))
File c:\Python26_32\lib\unittest.py, line 325, in failUnless
if not expr: raise self.failureException, msg
AssertionError
Note the 'svn' is not recognized as an internal or external command, in there.
Adam, does the build environment have Subversion installed and
accessible as svn on the path?
Hanno
___
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 Tests: 26 OK, 10 Failed, 5 Unknown
huh
weird, svn.exe is in c:\svn and it's on path:
excerpt from the log:
OS=Windows_NT
PATH=C:\svn;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\python25_sys;c:\python25_sys\scripts;C:\Program
Files (x86)\GnuWin32\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PY
On Tue, Jul 6, 2010 at 8:37 PM, Hanno Schlichting ha...@hannosch.eu wrote:
On Tue, Jul 6, 2010 at 1:58 PM, Zope Tests Summarizer
zope-te...@epy.co.at wrote:
Summary of messages to the zope-tests list.
Period Mon Jul 5 12:00:00 2010 UTC to Tue Jul 6 12:00:00 2010 UTC.
There were 41 messages: 6 from Zope Tests, 3 from buildbot at
enfoldsystems.com, 11 from buildbot at winbot.zope.org, 11 from ccomb at
free.fr, 1 from ct at gocept.com, 9 from jdriessen at thehealthagency.com.
Test failures
-
Subject: FAILED : winbot / ztk_dev py_265_win64
From: buildbot at winbot.zope.org
Date: Mon Jul 5 22:46:05 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016126.html
One of the test failures is this:
Running test-zopeapp-zope.app.applicationcontrol
test-zopeapp-zope.app.applicationcontrol failed with:
Running zope.app.applicationcontrol.testing.ApplicationControlLayer tests:
Set up zope.app.applicationcontrol.testing.ApplicationControlLayer
in 1.843 seconds.
Ran 4 tests with 0 failures and 0 errors in 0.516 seconds.
Running zope.testing.testrunner.layer.UnitTests tests:
Tear down zope.app.applicationcontrol.testing.ApplicationControlLayer
in 0.000 seconds.
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
'svn' is not recognized as an internal or external command,
operable program or batch file.
Failure in test test_WrongLocale
(zope.app.applicationcontrol.tests.test_zopeversion.Test)
Traceback (most recent call last):
File c:\Python26_32\lib\unittest.py, line 279, in run
testMethod()
File
c:\buildslave\ztk_dev_py_265_win32\build\src\zope.app.applicationcontrol\src\zope\app\applicationcontrol\tests\test_zopeversion.py,
line 136, in test_WrongLocale
self.assert_(zv.result.startswith('Development/Revision: '))
File c:\Python26_32\lib\unittest.py, line 325, in failUnless
if not expr: raise self.failureException, msg
AssertionError
Note the 'svn' is not recognized as an internal or external command, in
there.
Adam, does the build environment have Subversion installed and
accessible as svn on the path?
Hanno
--
Best regards,
Adam
___
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 )
