[Grok-dev] Migration to 1.0a3 -- and beyond

Uli Fouquet uli at gnufix.de
Wed Apr 15 18:35:09 EDT 2009

Hi there,

Am Mittwoch, den 15.04.2009, 13:49 -0300 schrieb Tim Cook:
> Okay,  Thanks to Uli for pointing out the link on PyPi about Grok
> startup upgrading (why hasn't this made it to grok.zope.org?) 

Hm, maybe because grokcore.startup is not internally bound to grok. In
fact it does not depend on a certain version of Grok.

> I know; this is FOSS and I need to pitch in too. But I'm so confused
> now.  After fixing my setup.py (beyond what the grok.startup document
> says when you are moving from an original 0.14 (1.0a1 didn't complain)
> to a 1.0a3 app).    

Yes, that might should be described more accurate. As said,
grokcore.startup does not depend on a certain version of Grok, but some
versions of grokproject generated this startup.py in new projects. The
upgrade notes therefore should refer to different grokproject versions.

> When I try to start the server I  get the following tracceback:
> ....(portions left out)
>   File
> "/home/tim/.buildout/eggs/grokui.admin-0.3-py2.5.egg/grokui/admin/docgrok.py", line 39, in <module>
>     from zope.app.apidoc.codemodule.module import Module
> zope.configuration.xmlconfig.ZopeXMLConfigurationError: File
> "/home/tim/oshipenv/oship/etc/site.zcml.in", line 4.2-4.29
>     ZopeXMLConfigurationError: File
> "/home/tim/oshipenv/oship/src/oship/configure.zcml", line 4.2-4.37
>     ZopeXMLConfigurationError: File
> "/home/tim/.buildout/eggs/grokui.admin-0.3-py2.5.egg/grokui/admin/configure.zcml", line 5.2-5.27
>     ImportError: No module named apidoc.codemodule.module
> So I breifly read that this was a problem with the Windows install.  But
> I using Ubuntu 8.10 

Unfortunanetly this is not a Windows-only problem. The new grokproject
version will fix all this, but we want to include some backslash
problems on windows before actually doing the next release.

> Just FYI to the authors and developers for the versions.cfg.  I
> commented out (not removed) the line about:
> # Here we pin the recipes and other packages that are not in the
> # downloaded versions.cfg of grok
> #grokui.admin = 0.3
> In order to avoid the previously reported "I can't decide error". 
> I note that 'apidoc' isn't in the versions.cfg file.  Should it be?

It is zope.app.apidoc which is missing, but as there are several other
packages in the zope.app namespace, Python only complains about missing

'zope.app.apidoc' is in the versions.cfg file, but I wonder if it
should. This way grokui.admin is more or less bound to the version
pinned down in groks version.cfg, while grok itself is not using
zope.app.apidoc. This might lead to problems like the ones with
grokcore.security. Hm, undecided.

Thanks, Tim, for the feedback!

Best regards,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090416/71aeabbd/attachment.bin 

More information about the Grok-dev mailing list