[Grok-dev] testing apps with grok-1.1a1

Simon Jagoe azriphale at gmail.com
Tue Dec 8 16:25:19 EST 2009

Hi all,

Good work on all of this. The only problem I have come across with
migrating to grok-1.1a1 is that the current release of megrok.login
does not support it. The problem is quite simple and easily fixed -
megrok.login.grokker has a call to grok.meta.setupUtility. Changing
this to use getUtility(IUtilityInstaller) seems to do the trick.
Anybody in a position to make this change upstream?


2009/12/1 Jan-Wijbrand Kolman <janwijbrand at gmail.com>:
> Jan-Wijbrand Kolman wrote:
>>> How about all of the grokcore.*
>>> packages, have those imports been migrated?
>> The grokcore.* family needs the same treatment. Mind though that for
>> some of these package there is a maintenance branch - for example
>> grokcore.view has one.
> I went through the grokcore.* packages:
> grokcore.annotation - migrated zope.app.container to zope.container.
> grokcore.component - no migration necessary.
> grokcore.formlib - migrated zope.app.container to zope.container (only
> used in tests).
> grokcore.security - migrated zope.app.security to zope.security. Since
> there is already a grokcore.component-2.0-compatible release for
> grokcore.security, we'll need to make a 1.2.1 "bugfix" release for grok-1.1.
> grokcore.view - was already done.
> All need releases of course, but if you guys could have a quick look at
> the changes first please...
> regards,
> jw
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list