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 ncoghlan
Recipients Dima.Tisnek, Dolf.Andringa, dstufft, exarkun, giampaolo.rodola, grooverdan, janssen, jcea, markk, mnot, ncoghlan, pdp, pitrou, sag47, scott.tsai
Date 2014-03-20.12:31:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1395313281.2300.1.camel@fsol>
I'm currently discussing some options with Donald and Christian. While it's
annoying that a developer from a certain large corporate user of Python (a
director of the PSF, no less) is whining at volunteers on the internet
instead of actually helping by encouraging their employer or the board to
help fund the creation and publication of an up to date TLS module for
Python 2, griping about the endemic problem of corporate users taking
community developed software for granted won't make the underlying problem
go away: an unfortunate amount of Python code is currently improperly
secured because it is using outdated SSL support, and there isn't currently
a good alternative available for users that aren't in a position to
immediately migrate to Python 3.
Date User Action Args
2014-03-20 12:31:48ncoghlansetrecipients: + ncoghlan, jcea, exarkun, janssen, pitrou, mnot, giampaolo.rodola, scott.tsai, pdp, grooverdan, Dolf.Andringa, Dima.Tisnek, dstufft, markk, sag47
2014-03-20 12:31:48ncoghlanlinkissue5639 messages
2014-03-20 12:31:48ncoghlancreate