[Python-Dev] PEP282 and the warnings framework

[Vinay Sajip]

> [Vinay]
> > The prevalent use and popularity of log4j and similar systems
> > underlines the
> > popularity of integer based severities; many man-years of
> > trial and error
> > and practical experience have gone into their current design,
> > and many good
> > brains have worked on them.
[Steve]
> This doesn't make it the best design.  Most of the numeric
> coding method was used because old computers were slow and
> small and simple integers (often only single bytes) were
> all that were practical.

I agree it doesn't make it the best design. But I don't think numeric coding
is used *just* because its space and time efficient - it's also more
intuitive. I don't think log4j is like it is because of platform
limitations.

> For example, Unix process termination status was only
> 7 of the 8 bits of a single bytes.
>
> This wealth of experience doesn't make this an optimal design;
> merely convenient for the available languages and processors.

I'm not sure "optimal" can be applied in this kind of context, in the true
sense. Depending on the kinds of applications you and I work on, "optimal"
for you might be different to "optimal" for me.

> I respect your passion for a complete implementation of the
> PEP.  I submit that the next generation should get past this
> "old/small" system technique and broaden the approach to use
> the full power of the Python class capabilities.

Please don't get me wrong. I'm not averse to using a new approach just
because it's new, nor is the present approach chosen because of "old/small".
The posts in this thread have got me thinking, but I don't know how long
it'll take me to "get it". I *still* can't see what it is you'd like to
achieve, but which you can't with the current functionality. A specific
example from a real application would sure help :-)

> Please look closely at the TIBCO subject-based messaging
> architecture.

Thanks. I will, time permitting - I'm not intimately familiar with the TIBCO
system but IIRC their messaging *is* the product - it's a full-blown
middleware layer. Probably much bigger than I can develop in my spare time
:-)

Regards, and thanks for your patience...


Vinay


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com