Hi, I noticed that in 2.1.6, subscription_cancel in Mailman/Cgi/confirm.py doesn't have the same SIGTERM unlocking parachute that subscription_confirm has; is this done on purpose, and why? Is there no risk of leaving a stale lock with what subscription_cancel does?
Without more info, I'd say this is "simply" oversight and that it would be needed. Your opinion? -- Lionel _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
