Hello,
it is evident that there is no consensus on the list of packages that are
part of the Zope Toolkit. As Gary suggested me, it looks like the concept
of ZTK is different for each developer and it is more or less "the packages
I use and I care about".
We need a policy to define the ZTK in an
Summary of messages to the zope-tests list.
Period Wed Aug 5 12:00:00 2009 UTC to Thu Aug 6 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Aug 5 20:50:47 EDT 2009
On 8/6/09 11:35 , Fabio Tranchitella wrote:
> I propose a (very) simple policy, which we can use to improve the current
> situation:
>
> * a package is part of the ZTK if the following criteria are met:
>
> - It has at least N zope developers (with commit rights) who
> explicitly expres
I just released Zope 2.12.0 beta 4
http://pypi.python.org/pypi/Zope2/2.12.0b4
Andreas
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. & Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
email;internet:i...@zopyx.com
title:CEO
tel;work:+49-7071-793376
tel;fa
* 2009-08-06 15:30, Wichert Akkerman wrote:
> How about another one:
>
> * the package has to be usable with all of Zope 2, grok and the Zope 3
>application server
Yep, I agree.
--
Fabio Tranchitella http://www.kobold.it
Free Software Developer and Consultant htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 8/6/09 11:35 , Fabio Tranchitella wrote:
>> I propose a (very) simple policy, which we can use to improve the current
>> situation:
>>
>> * a package is part of the ZTK if the following criteria are met:
>>
>> - It ha
Hello,
* 2009-08-06 17:03, Tres Seaver wrote:
> > How about another one:
> >
> > * the package has to be usable with all of Zope 2, grok and the Zope 3
> > application server
> >
> > That guarantees the stated goal that ZTK is reusable.
>
> I would restrict it to the "big toolkit" set whi
2009/8/6 Fabio Tranchitella :
> Am I correct saying that your idea is to restrict the ZTK to the packages
> defined as the intersection of the dependencies of zope2, zope3 and grok?
>
> ZTK = intersection ( zope2-dependencies , zope3-dependencies, grok )
That's my understanding of what Tres wrote
Hey,
Jim Fulton wrote:
[snip]
> Then the question is whether the dependence of zope.app.zcmlfiles on
> zope.app.interface is needed. I'll look to see what that's about.
For the record, I'd be happy to see zope.app.interface and
zope.app.module gone from our dependencies.
zope.app.zcmlfiles t
Hey,
Jim Fulton wrote:
> I think the KGS should define 3 categories of packages:
>
> - ZTK packages
>
>These are packages we maintain and expect people to build things on.
>
> - Test packages
>
> These are packages that build on the ZTK. These are used to test
> the ZTK packages, but
Lennart Regebro wrote:
> 2009/7/5 Stephan Richter :
>> To be honest, I am very disappointed by this list. It is totally meaningless
>> to me since it does not represent any list with which I can build even a
>> fairly simple application today. There is not a single z3c package in there.
>
> As I u
Fabio Tranchitella wrote:
> Hello,
>
> I just committed the removal of the dependency from zope.filerepresentation
> to zope.container, breaking the dependency cycle.
A belated yay! Thanks!
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
Hey,
Fabio Tranchitella wrote:
> I'd like to release some packages with fixed/improved dependencies:
>
> - zope.location
> - zope.sendmail
> - zope.pagetemplate
> - zope.app.publisher
> - zope.filerepresentation
>
> These packages are already ok in the repository, but I don't have the
Hey,
Stephan Richter wrote:
> - Insufficient dependency lists.
I wish we were publishing z3c.recipe.depgraph results for all these
packages in a convenient place. I'm worried that fixing dependencies
introduced cycles again (that were of course really there).
That's not to complain about all
Shane Hathaway wrote:
> Fabio Tranchitella wrote:
>> Is there a specific reason for having the version pinning? Automatic testing
>> of
>> zope.tales obviously fails using the KGS, because zope.traversing there is
>> 3.7.1.
>>
>> Is it possible to remove the "versions" stanza?
>
> Sure. Pinned v
Hey Fabio,
Fabio Tranchitella wrote:
> 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.
A belated +1 to discussing things, and +1 to doing work. :)
> I was analyzing zope.app.publish
Hey,
Andreas Jung wrote:
[snip]
> The diff between 3.5.1 and 3.5.2 is pretty long and substantial. I doubt
> that such a major change us ok as a bugfix release. I should have become
> a new major release.
From what you say, agreed.
Regards,
Martijn
___
Thomas Lotze wrote:
> There are two functions in zope.traversing.api, getParent and getParents,
> that are rather closely related. The former is implemented right in that
> module while the latter adapts its argument to
> zope.location.interfaces.ILocationInfo and calls getParents() on that.
>
> W
Hey,
Jim Fulton wrote:
> Well, um, we're in a position now where the various packages we've
> released don't seem to work together, because we've been releasing
> individual packages without running combined tests. I know this isn't
> your fault, but I'm queezy about doing more of this.
z
On Thu, Aug 6, 2009 at 12:31 PM, Martijn Faassen wrote:
> Hey,
>
> Fabio Tranchitella wrote:
>> I'd like to release some packages with fixed/improved dependencies:
>>
>> - zope.location
>> - zope.sendmail
>> - zope.pagetemplate
>> - zope.app.publisher
>> - zope.filerepresentation
>>
>> Th
On Thu, Aug 6, 2009 at 12:16 PM, Martijn Faassen wrote:
> Hey,
>
> Jim Fulton wrote:
>> I think the KGS should define 3 categories of packages:
>>
>> - ZTK packages
>>
>> These are packages we maintain and expect people to build things on.
>>
>> - Test packages
>>
>> These are packages that
Hey,
Fabio Tranchitella wrote:
> it is evident that there is no consensus on the list of packages that are
> part of the Zope Toolkit. As Gary suggested me, it looks like the concept
> of ZTK is different for each developer and it is more or less "the packages
> I use and I care about".
In a way
On Thu, Aug 6, 2009 at 1:05 PM, Martijn Faassen wrote:
> Hey,
>
> Fabio Tranchitella wrote:
>> it is evident that there is no consensus on the list of packages that are
>> part of the Zope Toolkit. As Gary suggested me, it looks like the concept
>> of ZTK is different for each developer and it is m
Hello,
* 2009-08-06 19:30, Martijn Faassen wrote:
> We need to get a procedure in place to do compat tests of what's in that
> list, dependency graph guarding of what's in that list, and locking down
> a KGS for that list. I think that since we have a list doing all these
> things is only a matter
Hello,
* 2009-08-06 18:55, Martijn Faassen wrote:
> > I was analyzing zope.app.publisher, and I found that it would be possible
> > to remove its dependency on zope.container because the latter is only used
> > in zope/app/publisher/xmlrpc/configure.zcml to declare thee views like
> > this:
> >
>
Fabio Tranchitella wrote:
> My knowledge of the zope.publisher is too limited to do any change in this
> area, but to me it looks like these configurations (both of them) should be
> perfomed by zope.app.publisher (removing the dependency zope.container ->
> zope.publisher), but conditionally (zcml
On 8/6/09 17:44 , Fred Drake wrote:
> 2009/8/6 Fabio Tranchitella:
>> Am I correct saying that your idea is to restrict the ZTK to the packages
>> defined as the intersection of the dependencies of zope2, zope3 and grok?
>>
>> ZTK = intersection ( zope2-dependencies , zope3-dependencies, grok )
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Drake wrote:
> 2009/8/6 Fabio Tranchitella :
>> Am I correct saying that your idea is to restrict the ZTK to the packages
>> defined as the intersection of the dependencies of zope2, zope3 and grok?
>>
>> ZTK = intersection ( zope2-dependencies ,
28 matches
Mail list logo
