[Grok-dev] anything blocking a Grok 1.1 release? and Grok 1.2 planning

Jan-Wijbrand Kolman janwijbrand at gmail.com
Thu May 20 08:03:19 EDT 2010

On 5/6/10 19:56 PM, Jan-Wijbrand Kolman wrote:
> * resurecting the "./bin/zopectl run [somepythinscript]" functionality.

This functionality is resurrected now, and in the process the way the 
interactive debugger commandline tool is created in a new project, has 
changed too. Instead of being an console_script entry_point in the newly 
created project, it is the buildout file that defines the tools.

The commandline tool now is based on the z3c.recipe.dev:script buildout 

It wraps the grokcore.startup.startup.interactive_debug_prompt() 
function. The zope.conf path of the project at hand is passed to this 
function as an argument (the interactive_debug_prompt function would 
otherwise basically guess the location of the zope.conf file...).

Whenever there're commandline argument passed to the 
./bin/interactive_debugger command, it will assume the first argument is 
a python script, like the "old" ./bin/zopectl command would have.

I think this resolves the last open grokproject issue.

grokcore.startup 1.0 is released now with this functionality. The grok 
1.0 bracn hhas been updated to use grokcore.startup 1.0. Likewise I have 
updated the groktoolkit trunk and 1.1 branch to include this new 
grokcore.startup version.

Note though that once the new grokproject is released, it will no longer 
be able to create projects for grok < 1.0.2 (that thus needs to be 


More information about the Grok-dev mailing list