I'm not sure whether mod_wsgi would be somehow different or not. initialize
is called in reviewboard/urls.py, which should definitely be invoked
regardless. If you're seeing the "Log file for Review Board ..." in the log
files, then you should be seeing signal connections. That is, unless
something broke in Django's signals, but you're using Django 1.1.x, right?
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Apr 20, 2010 at 12:33 PM, Stephen Gallagher <
> On 04/20/2010 03:31 PM, Christian Hammond wrote:
>> It shouldn't work for just one or the other. Try running
>> That connect_signals should be happening on the first request to Review
>> Board. Are you running this using fastcgi or mod_python?
>> Might also be worth checking to make sure that the following points are
>> also hit:
>> reviewboard/__init__.py: initialize
>> reviewboard/notifications/__init__.py: connect_signals
>> For what it's worth, e-mail notifications have been working here with 1.5
>> beta 1.
> I figured out what I had wrong with the tests. They seem to be passing
> (except the API tests, but that's expected).
> To answer your question, I'm actually using mod_wsgi, not mod_python. Is
> there an extra step I need to take to make sure that initialization takes
> Also, reviewboard/notifications/__init__.py: connect_signals is where I put
> my log message that was never printed.
> 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