In article <[EMAIL PROTECTED]> you write:
> Florent Guillaume wrote:
>
> > Ok I'll do the change so that the exception is reraised only in debug
> > mode AND if the user is not Manager (so that a Manager can still fix the
> > database).
>
> Great, thanks very much.
Ok it's on the trunk as r28478
Florent Guillaume wrote:
Ok I'll do the change so that the exception is reraised only in debug
mode AND if the user is not Manager (so that a Manager can still fix the
database).
Great, thanks very much.
Opinions on whether it can go on the 2.7 branch too ?
+0. Andreas is the final arbiter.
Tres.
In article <[EMAIL PROTECTED]> you write:
> Florent Guillaume wrote:
> > In _delObject and manage_beforeDelete there's a try/except that catches
> > nearly everything (except BeforeDeleteException and the infamous
> > ConflictError). It then proceeds to log a message, but continues:
> >
> >
Tres Seaver wrote at 2004-11-9 13:28 -0500:
>Florent Guillaume wrote:
> ...
>> In _delObject and manage_beforeDelete there's a try/except that catches
>> nearly everything (except BeforeDeleteException and the infamous
>> ConflictError). It then proceeds to log a message, but continues:
>>
>>
Florent Guillaume wrote:
In _delObject and manage_beforeDelete there's a try/except that catches
nearly everything (except BeforeDeleteException and the infamous
ConflictError). It then proceeds to log a message, but continues:
try:
object.manage_beforeDelete(object, self)
except
