[Zope-dev] Agenda for today's IRC meeting (3pm UTC on #zope)
Hi everyone, another weekly meeting is coming up today and I hope see you again around 3pm UTC at #zope at freenode. (That's a bit less than 4 hours from now on.) Last week's summary is here: https://mail.zope.org/pipermail/zope-dev/attachments/20100421/b1da5f70/attachment-0001. Agenda -- - State of bug tracking/LP usage - zope.app - emptying out Zope 3 bugs - dealing with the zope.org project group - Review bug day outcome - Windows machines status update Ongoing issues -- Those issues are currently ongoing. We don't have to discuss them. We just need to follow up on them eventually. - Bug tracking - Monitoring tracker status (Charlie Clark, ctheune) - Towards a ZTK release - Establishing ZTK release engineering team (Z2, grok, BB) - Documentation - Release scope - Test runners / nightly builds - Windows machines - Meta - How to organize open issues in the long run (Blueprints? Other tool? Continue text files?) - Find second person to run the weekly meetings Horizon --- These items are currently tracked on the horizon. We won't discuss them at this meeting, but we'll get to them at some point: - Pondering *some* (re-)structuring of the ZTK to allow for better maintenance/release management/communication/marketing. (Chris McDonough) 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 smime.p7s Description: S/MIME Cryptographic 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-dev] Zope Tests: 10 OK, 6 Failed
Summary of messages to the zope-tests list. Period Mon Apr 26 12:00:00 2010 UTC to Tue Apr 27 12:00:00 2010 UTC. There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 670 projects From: ct at gocept.com Date: Mon Apr 26 21:18:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014129.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Mon Apr 26 23:13:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014140.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Mon Apr 26 23:14:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014141.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Mon Apr 26 23:14:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014142.html Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Tue Apr 27 00:22:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014143.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Tue Apr 27 00:44:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014144.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 26 21:29:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014130.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 26 21:31:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014131.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Apr 26 21:33:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014132.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Apr 26 21:35:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014133.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Apr 26 21:37:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014134.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Apr 26 21:39:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014135.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon Apr 26 22:01:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014136.html Subject: OK : BlueBream template / Python2.7b1 32bit linux From: ccomb at free.fr Date: Mon Apr 26 22:01:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014137.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon Apr 26 22:01:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014138.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon Apr 26 22:01:30 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014139.html ___ 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.formjs on win32 + KGS
Hello Stephan, I think for the short time I'll just put it back to KGS, because the win32 tests have that much failures that if I would start to fix them the KGS will never be released. :-S OTOH, once the win tests pass it would be great to keep them that way. That means at least a buildbot is needed. Hopefully there will be some progress on that. Monday, April 26, 2010, 2:59:04 PM, you wrote: SR On Saturday 24 April 2010, Adam GROSZER wrote: * Use an other JSON converter (simplejson?) SR Definitely switch to simplejson. SR Regards, SR Stephan -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: A mind, like a home, is furnished by its owner, so if one's life is cold and bare he can blame no one but himself. - Louis L'Amour ___ 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] pypi access to zope.browserresource, zope.browsermenu
Stephan Richter wrote: On Monday 26 April 2010, Martijn Faassen wrote: Could someone give me and Hanno pypi access to zope.browserresource and zope.browsermenu? I am in the process to give you access to all the packages that I am an owner of (now that PyPI is fixed again. :-) Let me know if hannosch wants the same. Thanks! Thanks to you doing this in the previous round, I already was the owner already of a huge range of packages, but some of the ones that dropped out of refactorings were missing. I'll let Hanno speak for himself. :) 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.testing 4.0.0 coming up.
I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0. The backwards incompatibility is the following: 1. zope.testing.testrunner is now in it's own module, zope.testrunner. I will add a deprecation warning to trunk first, and we'll have to release a new zope.testing 3.x version, then 4.0.0 can be merged. 2. zope.testing.doctest will be dropped. There is already a deprecation warning about this. zope.testing 4.0.0 will support Python 3. Questions? :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64 ___ 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.testing 4.0.0 coming up.
On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro rege...@gmail.com wrote: I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0. ... Questions? :) Is it too late for me to introduce another mildly backwards incompatible change? I'd like to add a method to OutputFormatter to handle the specific case of layer setup/teardown failing and change the rest of the runner to call that instead of error. jml ___ 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.testing 4.0.0 coming up.
On Tue, Apr 27, 2010 at 21:49, Jonathan Lange j...@mumak.net wrote: On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro rege...@gmail.com wrote: I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0. ... Questions? :) Is it too late for me to introduce another mildly backwards incompatible change? I'd like to add a method to OutputFormatter to handle the specific case of layer setup/teardown failing and change the rest of the runner to call that instead of error. I have no opinion on this. How many tests break in Plone when you do this change? :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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] RFC: Proposed new style for documenting and testing ZTK packages
Am 17.04.2010, 03:41 Uhr, schrieb Tres Seaver tsea...@palladion.com: The trickier testing bits we would re-write as super thorough, no shortcuts-taken unit tests: one testcase class per class (or API function) under test, at least one method per class-under-test method, with more preferred to get all code paths / preconditions covered. The goal here would be to comment out the doctests from the test_suites and get the code to 100% coverage using pure unit tests. Meanwhile, the doctests would be refactored into the Sphinx documentation, losing all the bits which obscure their intent as documentation. I'm all for this but in the past I have struggled mightily (this could be an ironic use of the word ;-) with unit tests for views. Is this 1) Because I've overlooked something? 2) Because views depend on too many things, setting up test cases is a lot of work? 3) Because it's not been done a lot in the past? 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] zope.testing 4.0.0 coming up.
On Tue, Apr 27, 2010 at 3:30 PM, Lennart Regebro rege...@gmail.com wrote: I've been working on zope.tetsing lately. The main impetus behind this is Python 3 compatibility, but also general cleanup. This work was discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and me. The conclusion was to release a backwards incompatible zope.testing 4.0.0. The backwards incompatibility is the following: 1. zope.testing.testrunner is now in it's own module, zope.testrunner. I will add a deprecation warning to trunk first, and we'll have to release a new zope.testing 3.x version, then 4.0.0 can be merged. 2. zope.testing.doctest will be dropped. There is already a deprecation warning about this. zope.testing 4.0.0 will support Python 3. Questions? :) Just a comment that we should be prepared to maintain zope.testing 3 for some period of time. Maybe we should explicitly limit this period (e.g. through the end of 2010.) Jim -- Jim Fulton ___ 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 )
