Comment 7 for bug 524000

> I ran the latest trunk grokproject as you specified above, and it
> worked with your changes. The directory and file were created in
> "Documents and Settings\<user>" correctly. Grokproject successfully
> created the Sample project.

Great! That's the main point. I think we can close this bug now.
Thanks a lot Steve!

> I had a few issues running the resulting Sample project, but I don't
> think it was due to your changes. The problems were with particular
> zope packages and configuration and might have to do with the pulled
> versions being incompatible with Python 2.6. I believe it was pulling
> vesion 1.0 of Grok which I believe has issues with Python 2.6.

Exactly. 1.0 is not Python2.6-ready.

> I tried specifying 1.1a2 and it built but had different problems at
> runtime.

Hm, that _could_ be a problem (although this time not caused by
grokproject, I think). You could try specifying in buildout.cfg (of the
generated sample project):

extends =
   http://svn.zope.org/*checkout*/groktoolkit/trunk/grok.cfg

instead of 'versions.cfg'. That should fetch Grok 1.1a2 with an updated
list of dependent eggs/versions.

> I would be nice to try a new released Grokproject against a Grok 1.1a3
> with latest changes from JW and Souheil. I'm not sure that is planned
> though.

At least using an 'extends' like above should come near to what in the
end will be grok-1.1.cfg or grok-1.1a3.cfg, I think.

Before releasing grokproject I'd like to sort out two remaining things I
am not completely satisfied with. But that should be done until tomorrow
evening.

--Uli