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

Summary of messages to the zope-tests list. Period Fri Aug 7 12:00:00 2009 UTC to Sat Aug 8 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: Fri Aug 7 20:59:15 EDT 2009

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

On Fri, Aug 7, 2009 at 3:26 PM, Martijn Pieters wrote: > The following checkin fixed this particular problem: > >  http://svn.zope.org/Acquisition/trunk/src/Acquisition/_Acquisition.c?rev=102564&view=rev > > The acquisition slice wrapper accepted Py_ssize_t arguments, but then > passed these of as

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

On 08.08.09 14:19, Hanno Schlichting wrote: > On Fri, Aug 7, 2009 at 3:26 PM, Martijn Pieters wrote: > >> The following checkin fixed this particular problem: >> >> >> http://svn.zope.org/Acquisition/trunk/src/Acquisition/_Acquisition.c?rev=102564&view=rev >> >> The acquisition slice wrapper a

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

On Sat, Aug 8, 2009 at 13:19, Hanno Schlichting wrote: > One thing to note here is that the above change is indeed only of of > probably many that need to be made to support 64-bit platforms > properly. The other thing to note is that the change now introduces a > hard requirement on Python 2.5 or

Re: [Zope-dev] [Checkins] SVN: zope.publisher/trunk/ Moved dependency on zope.testing from install_requires to tests_require.

Hello, * 2009-08-08 16:20, Hanno Schlichting wrote: > On Sat, Aug 8, 2009 at 2:33 PM, Fabio Tranchitella wrote: > > Log message for revision 102578: > >  Moved dependency on zope.testing from install_requires to tests_require. > > I thought we were not using tests_require yet, as it doesn't work

Re: [Zope-dev] Some thoughts on KGS

Jim Fulton wrote: > On Thu, Aug 6, 2009 at 12:16 PM, Martijn Faassen > wrote: [snip] >> Could you give an example ofa 'test package'? I'm having trouble >> thinking of what these might be. > > Perhaps Grok (or keas ), or some higher-level framework or application > built with the framework. The

Re: [Zope-dev] Packages to be released

Hey, Jim Fulton wrote: > On Thu, Aug 6, 2009 at 12:31 PM, Martijn Faassen > wrote: [snip] > I certainly appreciate the participation. I'm sure you appreciate the > problem with breakage, although I'm not sure you appreciate it as much > as I do. :) I think we've had too much breakage. I think t

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

Jim Fulton wrote: [snip] > Except that the "under review" list is pretty long. Shall we include > everything that's under review as a starting point? We can always > lobby to remove some later. Yes, I'm +1 on being inclusive. I want to be pretty aggressive about removal, but we need to get from

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

Hey, Fabio Tranchitella wrote: [snip] > Jim suggested that zope.container shouldn't assume that I want to use > zope.publisher, and thus it is not a good idea to move the configuration of > the XMLRPC traversers to zope.container. I agree with that; I'd prefer zope.container to be publisher agnos

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

Hey, Fabio Tranchitella wrote: [snip] > I still think that starting from a very small list, allowing zope committers > to > add packages making an explicit commitment to maintain them would give us a > better overview of what does "ZTK" mean for each of us. I'm of the opposite opinion; let's sta

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

Fabio Tranchitella wrote: > 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 About the text on the wiki page: > Addition of new packages > > A new package can be added t

Re: [Zope-dev] KGS trunk without failures

Hey, Wolfgang Schnerring wrote: [snip] > After we reach a consensus on how to do it (I'm in favor of the way > outlined above, of course ;-), I'd like to add a step-by-step > walkthrough of the day-to-day development of a package somewhere below >

Re: [Zope-dev] KGS trunk without failures

Jim Fulton wrote: > (Note that I'm using more precise jargon: "project" rather than > "package". In the Python world, the word "package" means a module > that is implemented as a directory rather than a file. A project is a > collection of software for which we create distributions. We should > ge

Re: [Zope-dev] KGS trunk without failures

Hey, Wolfgang Schnerring wrote: > * Fabio Tranchitella [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 >>

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

Hey Jim, [optional integration and dependencies] Would it be possible to turn this into a guideline document somehow that we can include in the Zope Toolkit documentation? Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope

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

Hey, Jim Fulton wrote: [snip] > I do have some ideas for some specific minor cleanups in some of > these. (That had to do with zope.app.publication, not > zope.app.publisher.) That was blocked by the general instability we > have right now. I'd really like us to stop moving things around until >

Re: [Zope-dev] SVN: zope.publisher/trunk/ Moved dependency on zope.testing from install_requires to tests_require.

Hey, Fabio Tranchitella wrote: [snip] > In zope.component we use tests_require, in the very same way, for example. > Shall I remove it there, too? Is there a policy/document which explains how > we use extras and tests_require? Probably not. I think it'd be very good to add something like this to

Re: [Zope-dev] KGS trunk without failures

Hey Fabio, Fabio Tranchitella wrote: > * 2009-08-07 11:42, Wolfgang Schnerring wrote: >> [buildout] >> develop = . >> parts = compat >> extends = http://url/to/kgs/versions.cfg >> # assuming said versions.cfg uses a section called [versions]: >> versions = versions > > I've done something simila

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

sure. On Sat, Aug 8, 2009 at 1:26 PM, Martijn Faassen wrote: > Hey Jim, > > [optional integration and dependencies] > > Would it be possible to turn this into a guideline document somehow that > we can include in the Zope Toolkit documentation? > > Regards, > > Martijn > >

Re: [Zope-dev] SVN: zope.publisher/trunk/ Moved dependency on zope.testing from install_requires to tests_require.

On Sat, Aug 8, 2009 at 1:33 PM, Martijn Faassen wrote: > Hey, > > Fabio Tranchitella wrote: > [snip] >> In zope.component we use tests_require, in the very same way, for example. >> Shall I remove it there, too? Is there a policy/document which explains how >> we use extras and tests_require? > > P