[Ironpython-users] logging.handlers.NTEventLogHandler not in IP?

Hernán Foffani hfoffani at gmail.com
Fri Jan 13 19:27:17 CET 2012


El 13/01/2012, a las 19:05, Jeff Hardy escribió:

> On Fri, Jan 13, 2012 at 9:54 AM, Hernán Foffani <hfoffani at gmail.com> wrote:
>> 
>> El 13/01/2012, a las 18:49, Jeff Hardy escribió:
>> 
>>> On Fri, Jan 13, 2012 at 9:24 AM, Dino Viehland <dinov at microsoft.com> wrote:
>>>> I would think you could make your own NTEventLogHandler which wraps this,
>>>> you could probably contribute it back to the std lib under an if sys.platform == 'cli':
>>>> so that on IronPython you get the .NET NTEventLogHandler.
>>> 
>>> At the very list it could go into IronPython's stdlib. Until we can
>>> sync up with the 3.x branch I Don't know if we can push stdlib changes
>>> upstream.
>> 
>> Beware that the file that contains the NTEventLogHandler has some several more
>> classes. Won't it add some hassle to merge future std lib changes back to IP?
>> 
> 
> We already have a bunch of changes like it. Any extra hassle it adds
> is minuscule compared to the giant pain in the butt it already is
> (hence why it's not done very often).
> 
> For the 3.x branch I want to push as many changes as possible upstream
> to minimize that.

In that case I can provide a patch if you like.

(Sorry for the personal replies, didn't pay attention to the addressee in my previous
follow ups)




More information about the Ironpython-users mailing list