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 gregory.p.smith
Recipients gregory.p.smith, gvanrossum, tim.golden, vinay.sajip, zmk
Date 2012-04-12.07:03:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Your three step approach makes sense... But it _is_ still technically a new API though in that the UTF8BOM placeholder for LogRecord's is being introduced.  What would the behavior be when run on an older version without support for that placeholder be?

I'm okay with adding this but wouldn't be surprised if release managers are not.  But I personally have no need for syslog logging from Python so it'd be better to have someone who needs this to work properly chime in.

Perhaps just fixing it nicely in 3.3 is sufficient while documenting the misbehavior as a known issue for 2.7 and 3.2.
Date User Action Args
2012-04-12 07:03:51gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, vinay.sajip, tim.golden, zmk
2012-04-12 07:03:51gregory.p.smithsetmessageid: <>
2012-04-12 07:03:51gregory.p.smithlinkissue14452 messages
2012-04-12 07:03:51gregory.p.smithcreate