Re: (solved) smtplib, capturing output from set_debuglevel ??

From: Josiah Carlson (jcarlson_at_uci.edu)
Date: 10/08/04 

Date: Fri, 08 Oct 2004 12:30:17 -0700
To: "Tim Williams" <listserver@tdw.net>, python-list@python.org

> I decided to bite the bullet and have a look at the code for smtplib,
> (after being scared of changing it before), and of course its what I
> should have done in the first place.

I hope you didn't change your own copy of smtplib, but just subclassed
it. Changing a standard module is a good way to get bitten in the ass,
especially during Python upgrades.

In regards to changing the standard library's smtplib permanently, you
may or may not find support. A good way to find out is to post here
with the subject "proposed change to smtplib in standard library",
describe your changes, and if it has support, head to
sf.net/projects/python, list it as an RFE, and offer the code you have
written yourself.

 - Josiah

P.S. Did you get my post with the multi-threaded output? You get the
entire stream of debug data for a particular smtp thread in a single
string.

Relevant Pages

  • Re: Zen of Python
    ... There is a balance to be achieved however. ... might be better than "import smtplib", simply because making the standard ... library a package reduces the possibility of namespace collisions. ...
    (comp.lang.python)
  • Re: (solved) smtplib, capturing output from set_debuglevel ??
    ... server prog instead. ... As to subclassing, I took newbie fright and ran away from that. ... I get the modified smtplib into the production server and have a bit more ... > may or may not find support. ...
    (comp.lang.python)