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 lemburg
Recipients alex, dstufft, jeremy.kloth, larry, lemburg, ned.deily, pitrou, python-dev, steve.dower, zach.ware
Date 2015-04-14.00:56:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On 14.04.2015 01:36, Ned Deily wrote:
>> (certificate expiry checks not working)
> That issue appears to have been fixed in 1.0.2a, no?

Yes, but it shows the kind of errors to expect in the early
stages of a new branch. The above was a complete bummer.

However, I'm more concerned about the security issues that
were found so far in the 1.0.2 release. IMO, we should at least
wait for a 1.0.2b or 1.0.2c release before pushing 1.0.2 to
the users - at least for patch level releases of stable Python
versions such as Python 2.7 or 3.4.
Date User Action Args
2015-04-14 00:56:11lemburgsetrecipients: + lemburg, pitrou, larry, ned.deily, alex, jeremy.kloth, python-dev, zach.ware, steve.dower, dstufft
2015-04-14 00:56:10lemburglinkissue23686 messages
2015-04-14 00:56:09lemburgcreate