On Sat, May 16, 2009 at 10:47 AM, Chris McDonough chr...@plope.com wrote:
On 5/16/09 6:58 AM, Hanno Schlichting wrote:
Tres Seaver wrote:
+lots to calling this something other than 'repoze.zope2', which has
always been about bending over backward to provide full BBB for Zope2
apps.
On 5/12/09 11:54 AM, Hanno Schlichting wrote:
Chris McDonough wrote:
I think this package is becoming less repoze.zope2 than some other more
experimental system. Which is fine. But there's no way I'm going to be able
to give people help with it on IRC or the maillist when it breaks because
Chris McDonough wrote:
I added some more test coverage on the trunk. It's still pretty poor right
now.
Awesome!
I'll try to improve the coverage after getting some more documentation
for my latest changes in.
Hanno
___
Repoze-dev mailing list
Reed O'Brien wrote:
On May 12, 2009, at 12:17 PM, Chris McDonough wrote:
If we can't afford this (and I sure can't personally), I'm not sure
what we'd
end up calling it. plone.dot.someting? zope.dot.something?
ymmv.zope2
LOL! It would be a commitment to never commit to anything. :-)
Chris McDonough wrote:
I think this package is becoming less repoze.zope2 than some other more
experimental system. Which is fine. But there's no way I'm going to be able
to give people help with it on IRC or the maillist when it breaks because
they're using an API that we removed. I
2009/5/12 Chris McDonough chr...@plope.com:
If we ever do release an 80%-compatible publisher replacement, we should call
it
something other than repoze.zope2.
I doubt if we're really talking 80% though; if as Hanno suggests,
it'll run CMF, Plone and what other popular Zope 2 apps/libraries,
On May 12, 2009, at 12:17 PM, Chris McDonough wrote:
On 5/12/09 12:00 PM, Malthe Borch wrote:
2009/5/12 Chris McDonoughchr...@plope.com:
If we ever do release an 80%-compatible publisher replacement, we
should call it
something other than repoze.zope2.
I doubt if we're really talking
2009/5/12 Andrew Sawyers and...@sawdog.com:
Just and FYI from a (large) consumer of the repoze.zope2 package
This kind of change causes expensive test iterations. We're currently going
through one now...as a result of choosing to move over to repoze.zope2 and
friends. We would like to
