Release of zope.component (was [Checkins] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch)
I decided to start a new branch of that, because there's no still response on my requests for a release. Here's the last message:
Let's decide that and make a release of zope.component so we could move forward on adapting other packages to recent removal of BBB interfaces.
Here's three variants:
* Move pure python implementation to zope.hookable as a fallback. * Move C implementation to zope.component and drop zope.hookable dependency at all. * Just drop zope.hookable dependency, providing only pure python version of hookable.
The second (or even third, if there's no significant slowdown) variant seems fine to me personally, because, as Tres noted, there's probably no consumers for zope.hookable beyond zope.component, so we can safely merge the packages.
Jim, Philipp, Marius, can you please give us rights on PYPI for zope.component. My account is "nadako" there, so you can give it to me and I'll add other people.
-- WBR, Dan Korostelev
Hey, Dan Korostelev wrote:
I decided to start a new branch of that, because there's no still response on my requests for a release.
I see that you have access to that package now. Could you also give srichter access to zope.component? Regards, Martijn
2009/3/12 Martijn Faassen <faassen@startifact.com>:
Hey,
Dan Korostelev wrote:
I decided to start a new branch of that, because there's no still response on my requests for a release.
I see that you have access to that package now. Could you also give srichter access to zope.component?
Okay, done. Should we release it as it is currently (with pure-python hookables in itself but with "hook" extra that still pulls zope.hookable)? -- WBR, Dan Korostelev
Dan Korostelev wrote:
2009/3/12 Martijn Faassen <faassen@startifact.com>:
Hey,
Dan Korostelev wrote:
I decided to start a new branch of that, because there's no still response on my requests for a release. I see that you have access to that package now. Could you also give srichter access to zope.component?
Okay, done. Should we release it as it is currently (with pure-python hookables in itself but with "hook" extra that still pulls zope.hookable)?
Yes, I think that's all right. The work is already done and we risk the least in losing performance. Regards, Martijn
2009/3/12 Martijn Faassen <faassen@startifact.com>:
Dan Korostelev wrote:
2009/3/12 Martijn Faassen <faassen@startifact.com>:
Hey,
Dan Korostelev wrote:
I decided to start a new branch of that, because there's no still response on my requests for a release. I see that you have access to that package now. Could you also give srichter access to zope.component?
Okay, done. Should we release it as it is currently (with pure-python hookables in itself but with "hook" extra that still pulls zope.hookable)?
Yes, I think that's all right. The work is already done and we risk the least in losing performance.
Okay, it's released now. Expect some test breakage for the first time, until we adapt our packages to the removal of bbb interfaces. I'll try to do that quickly and then run the KGS and compat tests. -- WBR, Dan Korostelev
On Thursday 12 March 2009, Dan Korostelev wrote:
Okay, it's released now. Expect some test breakage for the first time, until we adapt our packages to the removal of bbb interfaces. I'll try to do that quickly and then run the KGS and compat tests.
With all these refactorings going on, we really should bring the test failures to 0 on the zope3.5 KGS, otherwise nobody pays attention. http://zope3.afpy.org/buildbot/waterfall Shrug, we are already at 26 failures and 18 errors. :-( I hope you guys realize how hard it is to get to 0/0. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
Stephan Richter wrote:
On Thursday 12 March 2009, Dan Korostelev wrote:
Okay, it's released now. Expect some test breakage for the first time, until we adapt our packages to the removal of bbb interfaces. I'll try to do that quickly and then run the KGS and compat tests.
With all these refactorings going on, we really should bring the test failures to 0 on the zope3.5 KGS, otherwise nobody pays attention.
http://zope3.afpy.org/buildbot/waterfall
Shrug, we are already at 26 failures and 18 errors. :-( I hope you guys realize how hard it is to get to 0/0.
Stephan, what would be involved to bringing this buildout to something.zope.org? Would that even be a good idea? The French Python association runs this now, right? We definitely need a link to this from somewhere in our documentation, as I personally don't remember this URL. Regards, Martijn
On Thursday 12 March 2009, Martijn Faassen wrote:
Stephan, what would be involved to bringing this buildout to something.zope.org? Would that even be a good idea? The French Python association runs this now, right?
We should ask ccomb (Chsristopher), though I think other people chipping in like this is a good idea, so we are not in the business of running a lot of servers.
We definitely need a link to this from somewhere in our documentation, as I personally don't remember this URL.
I agree. I have a bookmark to it. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
participants (3)
-
Dan Korostelev -
Martijn Faassen -
Stephan Richter