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 pitrou
Recipients exarkun, giampaolo.rodola, grooverdan, janssen, jcea, pdp, pitrou
Date 2010-05-24.16:18:47
SpamBayes Score 0.017007561
Marked as misclassified No
Message-id <1274717929.58.0.263990381191.issue5639@psf.upfronthosting.co.za>
In-reply-to
Content
> Python's main job is to make it *possible* to do things.  It's the
> application developer's job to decide what things should be done.

> It would be entirely appropriate, though, for a higher-level interface 
> (for example, the httplib module) to take care of this itself and not 
> require users to explicitly specify things separately.

Ok, I find this argument rather convincing. Also, enabling implicit SNI with the connect() argument could make user code stop working if he decides to pass the IP instead, without him being able to diagnose precisly what happens.

As you said, httplib/urllib should probably enable client-side SNI by default.
History
Date User Action Args
2010-05-24 16:18:49pitrousetrecipients: + pitrou, jcea, exarkun, janssen, giampaolo.rodola, pdp, grooverdan
2010-05-24 16:18:49pitrousetmessageid: <1274717929.58.0.263990381191.issue5639@psf.upfronthosting.co.za>
2010-05-24 16:18:48pitroulinkissue5639 messages
2010-05-24 16:18:47pitroucreate