[Grok-dev] grokproject status

Martijn Faassen faassen at startifact.com
Thu Apr 29 07:53:32 EDT 2010

Hey JW,

Jan-Wijbrand Kolman wrote:

> * grokproject will create a "buildout.cfg" that uses this information like so 
> (with 1.1rc1 taken as an example)::
>   [buildout]
>   extends = http://grok.zope.org/releaseinfo/1.1rc1/versions.cfg
>   extends-cache = cache

Is that the name of the directory that will be created? 'cache' is a bit 
of a generic word. I'd prefer if we called it 'versions' (that may be 
overly specific but is really what we're aiming at) or perhaps just 

> * The buildout.cfg file of a newly created project includes a [zpasswd] section. 
> It will create a cmdline tool based on code in zope.app.server to easily create 
> a zcml snippet for a new principal definition (including an correctly hashed 
> password). I do not like pulling in zope.app.server just for this feature - I 
> think it is nog used otherwise. So either we rip out this "feature" (is it used 
> by anyone?) or we re-create the script somehow - but where?

How does grokproject itself create the initial password? If it doesn't 
use zope.app.server, shouldn't the script we generate be able to use the 
same method?

> The development __of__ grokproject itself is now done solely in python2.6. The 
> reason was, that running the grokproject tests on Windows (on the buildbot for 
> example) will fail with missing binary eggs for python2.5. But I do not think 
> this is really a problem.	

Okay, as long as we do a manual test in Python 2.5 to see whether it 
works I think we'll be okay.

Thanks for the update!



More information about the Grok-dev mailing list