Jason Tackaberry wrote:
> On Thu, 2008-02-21 at 14:17 +0100, Dirk Meyer wrote:
>> Log:
>> expose AsyncExceptionBase
>
> Then you will need make_exception_class too, because one is not useful
> without the other. 

It is. But I miss-use it (see below)

> And if it's part of the external API, the name
> should probably be async_exception_metaclass
>
> Why do you need to expose AsyncExceptionBase?  Are you using it
> inside freevo?

For some stuff at work that will be part of Freevo later. My problem
is that I have an exception class, that takes an object and not a
string on __init__. And I use that exception async. If I do, your
metaclass somehow whats to create a new object of my class but only
has a string as parameter. Now your have the following code:

|   if not isinstance(value, AsyncExceptionBase):
|        value = AsyncException(value, stack)

The only way to avoid your AsyncException stuff is to inherit from
AsyncExceptionBase. I know it is ugly.


Dischi


-- 
This is Linux country. If you listen carefully, you can hear Windows
reboot...

Attachment: pgpdpF4VKwLDM.pgp
Description: PGP signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to