[Zope-dev] ZTK policy and package list (was Re: List of packages in the ZTK)

2009-08-07 Thread Fabio Tranchitella
I've created a policy draft as well as an initial list of packages on a wiki page, which I hope will help us to collaborate on the list: http://wiki.zope.org/zope3/ZTK I've put into the list the packages that I'd consider part of the ZTK and that I use in my applications. I don't know

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Wolfgang Schnerring
* Jim Fulton j...@zope.com [2009-08-02 18:34]: 2. Some of the tests only pass if run separately, due to test interactions. Presumably, this means that other tests aren't cleaning up after themselves. I think we need a standard automated way to run each package's tests separately. I think

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Fabio Tranchitella
Hello Wolfgang, * 2009-08-07 11:42, Wolfgang Schnerring wrote: [buildout] develop = . parts = whatever else you need compat extends = http://url/to/kgs/versions.cfg # assuming said versions.cfg uses a section called [versions]: versions = versions I've done something similar in

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Jim Fulton
Thanks Fabio and Wolfgang, How to do you specify the projects to be tested? Does every project in versions get tested? If so, how do you specify versions for projects that you don't want to run tests for but do want to fix the version of. (Note that I'm using more precise jargon: project rather

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Fabio Tranchitella
Hello Jim, * 2009-08-07 12:28, Jim Fulton wrote: How to do you specify the projects to be tested? Does every project in versions get tested? If so, how do you specify versions for projects that you don't want to run tests for but do want to fix the version of. In my recipe, it automatically

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Jim Fulton
2009/8/7 Fabio Tranchitella kob...@kobold.it: Hello Jim, * 2009-08-07 12:28, Jim Fulton wrote: How to do you specify the projects to be tested?  Does every project in versions get tested? If so, how do you specify versions for projects that you don't want to run tests for but do want to fix

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Wolfgang Schnerring
* Jim Fulton j...@zope.com [2009-08-07 06:01]: How to do you specify the projects to be tested? Does every project in versions get tested? If so, how do you specify versions for projects that you don't want to run tests for but do want to fix the version of. With z3c.recipe.compattest, to

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Wolfgang Schnerring
* Jim Fulton j...@zope.com [2009-08-07 12:39]: 2009/8/7 Fabio Tranchitella kob...@kobold.it: * 2009-08-07 12:28, Jim Fulton wrote: How to do you specify the projects to be tested?  Does every project in versions get tested? If so, how do you specify versions for projects that you don't want

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Wolfgang Schnerring
* Fabio Tranchitella kob...@kobold.it [2009-08-07 11:46]: * 2009-08-07 11:42, Wolfgang Schnerring wrote: http://svn.zope.org/*checkout*/zope.release/trunk/releases/controlled-packages.cfg IMHO the KGS testing should be done using the controlled-packages.cfg and not versions, because some

Re: [Zope-dev] KGS trunk without failures

2009-08-07 Thread Jim Fulton
On Fri, Aug 7, 2009 at 6:52 AM, Wolfgang Schnerringw...@gocept.com wrote: * Jim Fulton j...@zope.com [2009-08-07 06:01]: How to do you specify the projects to be tested?  Does every project in versions get tested? If so, how do you specify versions for projects that you don't want to run tests

[Zope-dev] Zope Tests: 3 OK, 4 Failed

2009-08-07 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Thu Aug 6 12:00:00 2009 UTC to Fri Aug 7 12:00:00 2009 UTC. There were 7 messages: 7 from Zope Tests. Test failures - Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Thu Aug 6 20:59:27 EDT

Re: [Zope-dev] Linux x86_64 [Was: Zope Tests: 3 OK, 5 Failed]

2009-08-07 Thread Martijn Pieters
On Mon, Aug 3, 2009 at 08:04, Martijn Pieters m...@zopatista.com wrote:  AssertionError: Incorrect Content-Length is set! Expected 20425,     got 20426. I don't grok the range support code at all:  probably Martijn Pieters is the only person in the world who does.  The tests are quite

Re: [Zope-dev] Linux x86_64 [Was: Zope Tests: 3 OK, 5 Failed]

2009-08-07 Thread Martijn Pieters
On Fri, Aug 7, 2009 at 14:55, Martijn Pieters m...@zopatista.com wrote: Here is the simple test case: from Acquisition import Implicit class Root(Implicit):    pass class Slicer(Implicit):    def __getslice__(self, start, end):        return [start, end] root = Root() slicer =

[Zope-dev] Optional integration need not introduce dependencies

2009-08-07 Thread Jim Fulton
In discussing dependencies, as we try to clean up dependencies of Zope (especially ZTK) projects, I've noticed a pattern that I think deserves some special handling. Often, a module (including a ZCML file) within a project provides an implementation of an interface defined by an external package

Re: [Zope-dev] Linux x86_64 [Was: Zope Tests: 3 OK, 5 Failed]

2009-08-07 Thread Martijn Pieters
On Fri, Aug 7, 2009 at 14:55, Martijn Pieters m...@zopatista.com wrote: The problem is caused by an acquisition wrapped object with a __getslice__ method get the wrong indices passed in when the end parameter is ommitted:  data[start:] Image.Pdata classes have a __getslice__ method, and

Re: [Zope-dev] Simplifying dependencies of zope.app.publisher

2009-08-07 Thread Jim Fulton
2009/7/8 Fabio Tranchitella kob...@kobold.it: Hello, I'm sorry if I am flooding the list with all my requests/messages, but I don't want to introduce changes without approval of more experienced zope developers. I was analyzing zope.app.publisher, and I found that it would be possible to

Re: [Zope-dev] Optional integration need not introduce dependencies

2009-08-07 Thread Roger Ineichen
Hi Jim Betreff: [Zope-dev] Optional integration need not introduce dependencies In discussing dependencies, as we try to clean up dependencies of Zope (especially ZTK) projects, I've noticed a pattern that I think deserves some special handling. Often, a module (including a ZCML

Re: [Zope-dev] Simplifying dependencies of zope.app.publisher

2009-08-07 Thread Jim Fulton
On Thu, Aug 6, 2009 at 4:39 PM, Shane Hathawaysh...@hathawaymix.org wrote: ... I'm hoping Jim will soon take charge of zope.publisher, zope.traversing, zope.container, and zope.app.publisher, because he seems to be the only one who knows how they are supposed to be related. Hah. Thanks a lot.

[Zope-dev] XMLRPC support (was Re: Optional integration need not introduce dependencies)

2009-08-07 Thread Jim Fulton
On Fri, Aug 7, 2009 at 10:51 AM, Roger Ineichend...@projekt01.ch wrote: ... I think XML-RPC just belongs to an own package e.g. zope.xmlrpc. It doesn't make sense to have XML-RPC in a package other then an own. Agreed, although moving it out would introduce a backward incompatibility. Maybe

Re: [Zope-dev] List of packages in the ZTK

2009-08-07 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabio Tranchitella wrote: Hello, * 2009-08-07 05:28, Fred Drake wrote: In particular, I would exclude any package in the zope.app.* namespace which is not also used by either grok or Zope2. As would I. Fine, I plan to work on this today,

Re: [Zope-dev] Simplifying dependencies of zope.app.publisher

2009-08-07 Thread Jim Fulton
2009/8/7 Fabio Tranchitella fa...@tranchitella.it: Hey Jim, you picked up an old e-mail of mine (it is from 8th of July)! :) I know, but I thought my response was most applicable to the original. :) * 2009-08-07 17:13, Jim Fulton wrote: For now, make these registrations conditional on the