If you're running through apache, you'll have to at least do a "reload"
(which is like a restart but it just reloads its configuration). If it's not
obvious how to do that, then a restart will also work.
It's usually easier to use django's built-in web server while making code
changes, because it will automatically reload when it notices that the
python files change.
how to use this.
On Wed, Mar 9, 2011 at 9:01 PM, Vivek Subramanian <
> Hi Christian,
> It took me time but I think I have managed to write very bad python code to
> do what you described. It basically piggbacks on the
> review_request_published signal. (I simply wrote an almost identical signal
> like review_request_published with the same bunch of arguments and also sent
> from exactly the same place). Only the handler for this signal in the
> notification/email.py is different. It tries to get hold of the the bugs
> from the review request object.
> What I am trying to do is simply log these bugs into a file so that I can
> test my changes, but for some reason I haven't figured out how to check if
> my code is being called.
> My basic problem is that if I change something in the reviewboard source,
> then what are the steps I should take to make sure that this code is called
> - as in do I have to just restart the webserver etc?
> I am really sorry, but I am totally new to python as such.
> Best regards,
> On Fri, Mar 4, 2011 at 2:36 AM, Christian Hammond <chip...@chipx86.com>wrote:
>> Hi Vivek,
>> There's nothing built-in to do this. The plan, after the currently
>> in-development 1.6 release, is to focus almost solely on our extension
>> framework and get that into a 2.0 release. At that point, it'll be possible
>> to build functionality into the product for updating bug trackers and other
>> For now, there is a hack you can do, though I can't fully walk you through
>> it (it'd take some experimentation).
>> In your site's conf/settings_local.py, you should be able to append to the
>> INSTALLED_APPS tuple (which is provided by Review Board's
>> reviewboard/settings.py). You'd append the name of a small Python module
>> you'd write and install on the server. This module, in __init__.py, would
>> listen for the signals Review Board emits on different review request
>> operations (see reviewboard/reviews/signals.py and look up the standard
>> Django signals for models). You should be able to listen to these and react
>> with a call to your script.
>> There may be some issues in doing this, I don't know. Certainly long-term,
>> it may not continue to work correctly. But perhaps that'd be a start?
>> Christian Hammond - chip...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> VMware, Inc. - http://www.vmware.com
>> On Thu, Mar 3, 2011 at 1:34 AM, Vivek Subramanian <
>> subramanian.vi...@gmail.com> wrote:
>>> We use bugzilla for tracking our bugs and as part of the process of
>>> posting a review we need to put in a comment on the bug with a link to the
>>> review topic. I understand that this is currently not available in
>>> ReviewBoard. I already have a perl script which does this - given the bug
>>> number and the comment to post on the bug, it can go and update bugzilla.
>>> I'd like to know if there is some way to do this currently in the 1.5
>>> release that we are using - calling this perl script I have from within rb.
>>> Is this possible to do this by adding a small hook in the python code?
>>> Best regards,
>>> Want to help the Review Board project? Donate today at
>>> Happy user? Let us know at http://www.reviewboard.org/users/
>>> To unsubscribe from this group, send email to
>>> For more options, visit this group at
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at