Message 167555 - Python tracker

➜

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.

In-reply-to
Author	tweksteen
Recipients	chris.jerdonek, pitrou, tweksteen
Date	2012年08月06日.12:24:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1344255880.95.0.666043676639.issue15464@psf.upfronthosting.co.za>

Content
When I wrote this patch, I was focusing on a particular usage and the buffer was the only parameter that interested me. But you're right, the other parameters should be included. Which brings the following questions: * write_p looks like a boolean, would it be appropriate to make it like that? Or keep it integer? * version can be SSL2_VERSION , SSL3_VERSION or TLS1_VERSION. However, these constants are not used yet in _ssl. Should they be mapped to the current ones (with the tricky exception of PROTOCOL_SSLv23)? * content_type could just be passed as a regular integer. Thanks

Content

When I wrote this patch, I was focusing on a particular usage and the buffer was the only parameter that interested me. But you're right, the other parameters should be included. Which brings the following questions:
* write_p looks like a boolean, would it be appropriate to make it like that? Or keep it integer?
* version can be SSL2_VERSION , SSL3_VERSION or TLS1_VERSION. However, these constants are not used yet in _ssl. Should they be mapped to the current ones (with the tricky exception of PROTOCOL_SSLv23)?
* content_type could just be passed as a regular integer.
Thanks

History
Date	User	Action	Args
2012年08月06日 12:24:41	tweksteen	set	recipients: + tweksteen, pitrou, chris.jerdonek
2012年08月06日 12:24:40	tweksteen	set	messageid: <1344255880.95.0.666043676639.issue15464@psf.upfronthosting.co.za>
2012年08月06日 12:24:40	tweksteen	link	issue15464 messages
2012年08月06日 12:24:38	tweksteen	create

homepage