Source line number for log purpose (newbie)

[T. C. Mits]

Interesting and great code ideas regarding logging.

I'm wondering if there is a need for a framework for this kind of stuff.
But since requirements are so unique in relation to logging, more explicit
code or documentation for support of this usage (It's probably me, but the
traceback and other libraries are sometimes hard to use without a more
expert grasp of the total Python details; more HOWTOs are needed).

François Pinard <pinard at iro.umontreal.ca> wrote in message
news:oqhfki75y3.fsf at titan.progiciels-bpi.ca...
> Siggy Brentrup <bsb at baal.infodrom.north.de> écrit:
>
> > Just another idea: abuse a functions __doc__ string
>
> :-) :-)
> I should surely at least learn using them, before abusing them...
>
> > Btw, do you grant permission to use, copy and modify ...?
>
> Yes, no problem in this case.  Conditions are not clearly stated, it's
true.
> For FSF works, I was using the big legalistic GPL comment which is usual
> to them, but otherwise, I just use three lines, routinely, in almost every
> file I write, and I merely included a whole file in my previous message.
> Maybe it would be wiser to add a fourth line summarising copying
conditions,
> but that would make a _lot_ of files to modify :-).
>
> --
> François Pinard   http://www.iro.umontreal.ca/~pinard
>
>
>