[Zope-dev] Re: undeprecating zLOG

[Andreas Jung]

--On 2. Februar 2007 15:09:53 +0100 Philipp von Weitershausen 
<philipp at weitershausen.de> wrote:

> Tres Seaver wrote:
>> Chris Withers wrote:
>>> Andreas Jung wrote:
>>>> 0, for keeping zLOG for the time being...
>>>> -1, for undeprecating it. Using Python's logging module should remain
>>>> the only recommended solution. I don't want to see any new code using
>>>> zLOG.
>>
>> +1 for undeprecating it -- the noise it generates is usesless, and the
>> value which its (attempted) removal has sucked out of our development
>> process is far greater than any "hygeine" it was intended to create.
>> At this point, the module is a thin compatibility wrapper for the
>> logger, and no more.
>>
>> If *we* introduced lots of bugs into Zope trying to rip out zLOG from
>> the core, why should we induce that same hell on people maintaining
>> third-party products?
>
> That is a good point. I should note that the deprecation of zLOG happened
>
> a) without a proper proposal that *exactly* outlined how certain zLOG
> calls should be spelled. Such proposals serve as reference for everyone
> who has to update their code.
>
> b) without moving the whole Zope 2 codebase to the new API. That in turn
> ended up in a desaster because the different places zLOG was still used
> were fixed up one by one by different people who made mistakes (mostly
> because of point a)).
>
> I think those points account for some of the problems we've had; there
> have certainly been wilder refactorings that people could deal better
> with because they were better documented.
>
> Nevertheless, the proposed benefits (less code to maintain, etc.) don't
> seem to balance the effort we've needed even just for Zope core at this
> point. As said, I wouldn't mind if zLOG was added back and even
> undeprecated, just as much as I wouldn't mind keeping the current
> situation.
>

If anyone is interested in putting zLOG back into the core, put it back.

However I am still opposed removing the deprecation. It should remain 
deprecated without the threat to remove it in Zope 2.11. That's a clear 
message to avoid using zLOG for new code. The recommended solution for 
logging in Zope 2 country is and will be the 'logging' module of Python.

Andreas


>
> --
> http://worldcookery.com -- Professional Zope documentation and training
> Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope )



-- 
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: info at zopyx.com - Phone +49 - 7071 - 793376
Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535
Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK
------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20070202/8b20b813/attachment.bin