Hi there, There are two alternative patches provided to add a single extra API item for this package, which would allow developers the ability to extend the logging package to a certain extent without clobbering each other's work. At present, it isn't possible for a package to customise the logging.Logger class, without running the risk of having it's changes clobbered by an application using the package, or another package. This small change allows each customiser to inherit changes from the last customiser. Any chance of getting one of these solutions in for 2.4? the "loggerClass" option provides more respectable declaration syntax, but the "getLoggerclass" option provides symmetry. http://sourceforge.net/tracker/index.php?func=detail&aid=1032206&group_id=5470&atid=305470 Thanks, David. -- The next great adventure of mankind is not for people who ask, "What exactly is the point?" They will never get it. -- http://news.bbc.co.uk/1/hi/sci/tech/3302375.stm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4