_q_exception_handler

Hi all,

I am new in the list, I use destar and it migrated to
quixote 2, and the 
_q_exception_handler is not called anymore, How could I
change the 
_q_traverse to point to _q_exception_handler?

Thanks

Ian Esper
_______________________________________________
Quixote-users mailing list
Quixote-usersmems-exchange.org
http://mail.mems-exchange.org/mailman/listinfo/quixo
te-users

Ian Esper <ianbratech.com.br> wrote:
> I am new in the list, I use destar and it migrated to
quixote 2, and the 
> _q_exception_handler is not called anymore, How could I
change the 
> _q_traverse to point to _q_exception_handler?

The publish1 module should support _q_exception_handler but
it
currently doesn't.  Sorry.  If anyone cares to implement it
then I
would be happy to integrate it.

You have a couple of choices, I think.   You could use the
publish1
module and implement the _q_exception_handler support. 
That
shouldn't be too hard but it's a little harder than a
straight copy
of code from the quixote-1.x package.

You could implement support for something like
_q_exception_handler
on a Directory subclass.

Finally, if you only have a few _q_exception_handler hooks
then you
could just override the _q_traverse method on the relevant
Directory
objects.  Something like:

    def _q_traverse(self, path):
        try:
            return Directory._q_traverse(self, path)
        except PublishError:
            ... exception handling code
        
Regards,

  Neil

_______________________________________________
Quixote-users mailing list
Quixote-usersmems-exchange.org
http://mail.mems-exchange.org/mailman/listinfo/quixo
te-users

Hi Neil,

Thanks for answer, I'll try to implement it next week.

Ian
Neil Schemenauer escreveu:
> Ian Esper <ianbratech.com.br> wrote:
>   
>> I am new in the list, I use destar and it migrated
to quixote 2, and the 
>> _q_exception_handler is not called anymore, How
could I change the 
>> _q_traverse to point to _q_exception_handler?
>>     
>
> The publish1 module should support _q_exception_handler
but it
> currently doesn't.  Sorry.  If anyone cares to
implement it then I
> would be happy to integrate it.
>
> You have a couple of choices, I think.   You could use
the publish1
> module and implement the _q_exception_handler support. 
That
> shouldn't be too hard but it's a little harder than a
straight copy
> of code from the quixote-1.x package.
>
> You could implement support for something like
_q_exception_handler
> on a Directory subclass.
>
> Finally, if you only have a few _q_exception_handler
hooks then you
> could just override the _q_traverse method on the
relevant Directory
> objects.  Something like:
>
>     def _q_traverse(self, path):
>         try:
>             return Directory._q_traverse(self, path)
>         except PublishError:
>             ... exception handling code
>         
> Regards,
>
>   Neil
>
> _______________________________________________
> Quixote-users mailing list
> Quixote-usersmems-exchange.org
> http://mail.mems-exchange.org/mailman/listinfo/quixo
te-users
>
>   

_______________________________________________
Quixote-users mailing list
Quixote-usersmems-exchange.org
http://mail.mems-exchange.org/mailman/listinfo/quixo
te-users