On Mon, Jan 22, 2007 at 02:55:31PM +0100, Emmanuel Blot wrote:

> It does not imply that the code in notification.py is valid, but the
> syntax is.

Thank you Manu for the clarification.
The main reason why I ask:
I have in trac.ini:

always_notify_owner = true
always_notify_reporter = true
always_notify_updater = false

Now, if changes are made to a ticket, and owner == updater, notification
is sent to the owner too, which makes little sense only, since the owner
should now what he has done.
So I dived into notification.py and saw lines 230ff:

-----8<-----
# Suppress the updater from the recipients
for updater, in cursor:
  break
else:
  cursor.execute("SELECT reporter FROM ticket WHERE id=%s", (tktid,))
  for updater, in cursor:
    break

if not notify_updater:
  filter_out = True
  if notify_reporter and (updater == self.reporter):
    filter_out = False
  if notify_owner and (updater == self.owner):
    filter_out = False
  if filter_out:
    torecipients = [r for r in torecipients if r and r != updater]
elif updater:
  torecipients.append(updater)

return (torecipients, ccrecipients)
-----8<-----

I am trying to understand what this block does (especially "torecipients
= [r for r in torecipients if r and r != updater]"), since I think my
problem is here in this block.

Rainer

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to