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 eric.araujo, ncoghlan, richard, steve.dower, takluyver, tim.golden, zach.ware
Date 2015-04-25.07:41:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429947691.76.0.91543749555.issue23955@psf.upfronthosting.co.za>
In-reply-to
Content
I'd actually like a python.ini file defined as a Python 3.5 feature in order to provide a better backporting story for the PEP 476 certificate changes in downstream long term support releases of Python 2.7.

So +1 in principle, but I'd like to see this written up as a PEP (the SSL configuration setting doesn't need to be in the PEP, but the optional existence of the config file and reading it at startup does).
History
Date User Action Args
2015-04-25 07:41:31ncoghlansetrecipients: + ncoghlan, richard, tim.golden, eric.araujo, takluyver, zach.ware, steve.dower
2015-04-25 07:41:31ncoghlansetmessageid: <1429947691.76.0.91543749555.issue23955@psf.upfronthosting.co.za>
2015-04-25 07:41:31ncoghlanlinkissue23955 messages
2015-04-25 07:41:31ncoghlancreate