[Grok-dev] spotlight on: megrok.traject

Gary Poster gary.poster at gmail.com
Mon Jan 25 13:00:09 EST 2010

On Jan 25, 2010, at 12:53 PM, Martijn Faassen wrote:

> Hey Ethan,
> Ethan Jucovy wrote:
>> On Mon, Jan 18, 2010 at 4:21 PM, Martijn Faassen <faassen at startifact.com 
>> 3) Add the line `os.environ['DJANGO_SETTINGS_MODULE'] = 
>> ${something_from_buildout}` to bin/myproject-ctl, bin/paster, etc.  I 
>> think this is the most straightforward and correct place to put that 
>> line, if it's not too difficult to modify buildout's script templates.
> I'd be nice if we could avoid creating a separate project + template.
> What you could do is create a 'grongo' or 'megrok.django' module that:
> * has the Django and megrok.traject dependencies
> * also creates the script when listed in the dependencies (not sure 
> whether it'd need a special buildout to stop this)
>> Task #3 is the one I'm least confident about.  I haven't found any
>> obvious way to do this.  I'd be very grateful if somebody with more
>> buildout knowledge could point me in the right direction, or tell me
>> I'm approaching this wrong and give me a different direction.  :)
> Adding this stuff to paster seems to be difficult to do. But would we
> be able to add a plugin mechanism to either grokproject or 
> grokcore.startup that you could hook this into?

I take it the zc.recipe.egg "initialization" option is insufficient?


Is it insufficient because some aspect of this needs to happen within paster?

(My curiosity is largely limited to whether the zc.recipe.egg script could be improved in this regard, though +1  on the Django/Grok combo experiment.)


More information about the Grok-dev mailing list