This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Rhodri James, ethan.furman, serhiy.storchaka, thatiparthy, vinay.sajip
Date 2020-07-02.18:49:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593715784.77.0.528963532751.issue41139@roundup.psfhosted.org>
In-reply-to
Content
Available options:

1. Do nothing (keep cgi.log() and continue to use the default encoding for open()).
2. Remove cgi.log(). I think that the deprecation period is not needed because the function is not documented, is not imported by star-import, and is not shown in help.
3. Make cgi.log() using UTF-8 for open(). This may break some existing code if cgi.log() is ever used.
4. Completely rewrite cgi.log() using the logging module.

In all options except 2 cgi.log() needs to be documented and advertised as a new feature. And we should ask ourself: do we need this feature? Does it have advantages over the logging package?

It was more visible in 2.0. But since adding __all__ in 2.1 (in e99d5ea25ba994491c773d9b5872332334ccd1c5) it is a hidden feature.
History
Date User Action Args
2020-07-02 18:49:44serhiy.storchakasetrecipients: + serhiy.storchaka, vinay.sajip, ethan.furman, thatiparthy, Rhodri James
2020-07-02 18:49:44serhiy.storchakasetmessageid: <1593715784.77.0.528963532751.issue41139@roundup.psfhosted.org>
2020-07-02 18:49:44serhiy.storchakalinkissue41139 messages
2020-07-02 18:49:44serhiy.storchakacreate