Re: Python bindings

Thanks for the explanation, I see it clearly now ;)

>  That is why my current thinking is to ship
> the python/mrproject.c file in the distributed tarball and only
> regenerate it at build time if the tools are available. I would be
> reluctant to check it into CVS, though, so PyGTK (or at least the
> codegen portion) will still be required for that.

We have no problem with that. If you are building from CVS, I think not
having pygtk is your smallest problem ;) 

> If this is still not clear, please let me know and I will try again
> (although I should be able to finish it up over the weekend and you will
> be able to see what I am talking about).

Crystal clear, sounds good! 

Thanks,
Richard

-- 
Richard Hult                    [email protected]
CodeFactory AB                  http://www.codefactory.se/