[issue22301] smtplib.SMTP.starttls' documentation is just confusing

Christian Heimes added the comment: starttls() does accept a ssl_context argument for a while. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

Michele Orrù added the comment: "R. David Murray" writes: > Since we want to encourage people to use the context, that sounds > reasonable for 3.x at least. Concerning this specific proposition, I really don't see the point in having .starttls() not simply accepting a SSLContext as argument, a

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

R. David Murray added the comment: Remove the reference, you mean? As in just delete the confusing line? Since we want to encourage people to use the context, that sounds reasonable for 3.x at least. -- ___ Python tracker

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

Antoine Pitrou added the comment: Or perhaps we should remove the function to wrap_socket(), which is just an implementation detail? -- ___ Python tracker ___ __

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

Changes by Terry J. Reedy : -- stage: -> patch review versions: -Python 3.1, Python 3.2, Python 3.3 ___ Python tracker ___ ___ Pytho

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

Alex Gaynor added the comment: Attached patch fixes this up. -- keywords: +needs review, patch nosy: +alex Added file: http://bugs.python.org/file36505/t22301.diff ___ Python tracker ___

[issue22301] smtplib.SMTP.starttls' documentation is just confusing

New submission from Michele Orrù: hello! In I read:: "If keyfile and certfile are provided, these are passed to the socket module’s ssl() function." socket.ssl() exists, though it is not documented (not even in /dev/libr