[Zope-dev] Zope Tests: 15 OK, 1 Failed
Summary of messages to the zope-tests list. Period Sat May 15 12:00:00 2010 UTC to Sun May 16 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 582 projects From: ct at gocept.com Date: Sat May 15 21:18:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014443.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 15 21:29:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/01.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 15 21:31:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014445.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Sat May 15 21:33:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014446.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Sat May 15 21:35:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014447.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Sat May 15 21:37:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014448.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Sat May 15 21:39:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014449.html Subject: OK : BlueBream template / Python2.7b2 32bit linux From: ccomb at free.fr Date: Sat May 15 22:00:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014450.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sat May 15 22:00:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014451.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Sat May 15 22:00:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014453.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sat May 15 22:00:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014452.html Subject: OK : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Sun May 16 00:04:00 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014454.html Subject: OK : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Sun May 16 00:05:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014455.html Subject: OK : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sun May 16 00:05:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014456.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sun May 16 00:25:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014457.html Subject: OK : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sun May 16 00:49:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014458.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] ztk checkversions script
Le 04/05/2010 00:04, Christophe Combelles a écrit : Vincent Fretin a écrit : On Sun, May 2, 2010 at 10:52 PM, Martijn Faassenfaas...@startifact.com wrote: Hi there, Of course what applies to Hanno should apply to others making releases of packages maintained by the Zope Toolkit project as well. I think the ZTK leadership should figure out some kind of guidelines for this that people can follow. Maybe someone can write a tool too to check up how far a toolkit is out of sync with the latest releases. Just some ideas. For the tool, I think I did it already. I modified one of Hanno's script some times ago: cd zopetoolkit/trunk bin/buildout -c checknew.cfg bin/python checknew.py I have already started to turn this script into a buildout recipe (probably z3c.recipe.checknew). I will make sure it can discover either minor bugfix versions or major versions, and be able to create a versions.cfg. It's now released as z3c.checkversions http://pypi.python.org/pypi/z3c.checkversions It's not a recipe but a console_script. So that it can be used in a virtualenv as well, without buildout. For a buildout, you just have to add it in the buildout eggs: it creates a checkversions script that can detect new versions (minor or major, depending on the -l option). Christophe Christophe Vincent ___ 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 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 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] Zope2 - Breaking out more packages
Hi. I've started working some more on my pet project of refactoring Zope2 - specifically to move all C code to external distributions. My working branch is at svn+ssh://svn.zope.org/repos/main/Zope/branches/hannosch-dtml-vs-accesscontrol which also has a TODO.txt with some notes. On the branch DocumenTemplate imports from AccessControl but not the other way around. So in general I think this can be made to work. My current plan involves: - Move Shared.TaintedString to an external distribution. It's used both by DocumentTemplate and ZPublisher. Moving it into DocumentTemplate and have ZPublisher depend on it, sounds like a poor choice to me - a publisher shouldn't depend on a markup language. We could also move it into AccessControl as it's sort of a security feature. - Move zExceptions to an external distribution. It's used from all over, but has no external dependencies on its own. Instead of just moving it out, I'd look at merging some of it into zope.exceptions. The two share a good deal of code like the exception formatter and common exception classes. - Move the ZMI parts of AccessControl into the App package. App already holds a good deal of general ZMI pages, so this seems a good fit. It basically makes App the zope.app of Zope2. There's a bunch of more minor stuff to work out and lots of awful test dependencies, but in general it looks good. If you have any feedback on the above, please shout - otherwise I'll continue as planned and time permits. Once this is finished and merged, ZCTextIndex holds the last bits of C code inside the Zope2 distribution - there's multiple ways to deal with it: break it and HelpSys out or reuse the C code from zope.index. We can look at that later. 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 )
