My mailer just barfed trying to read that summary.
The problem is that the mail comes out with the encoding:
Content-Type: text/plain; charset="us-ascii"
but then wants to print 'http://bugs.python.org/issue25709 opened
by Ãrpád Kósa'
Can we change the encoding to utf-8 ?
Laura
_
ACTIVITY SUMMARY (2015-11-20 - 2015-11-27)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open5263 ( +3)
closed 32238 (+57)
total 37501 (+60)
Open issues wit
Hi,
As R. David Murray wrote on the issue, the python-ideas mailing list
is better suited to start such discussion ;-)
Victor
2015-11-27 9:40 GMT+01:00 王珺 :
> Hello everyone:
>
> I'm suggesting a modification to the AttributeError/__getattr__ mechanism,
> see issue25634:
> http://bugs.python.org
Hello everyone:
I'm suggesting a modification to the AttributeError/__getattr__ mechanism,
see issue25634:
http://bugs.python.org/issue25634
I used __getattr__ sometimes, and *descriptor* especially *property* is so
widely used. I wonder whether someone
had encountered the same problem with me.
On 27 November 2015 at 18:47, Cory Benfield wrote:
> Perhaps I missed this, Nick, but what happens if multiple third party
> libraries apply updates to call this function in incompatible ways? For
> example, if you depend on libfoo which calls
> ssl._verify_https_certificates(False) and libbar
> On 27 Nov 2015, at 06:04, Nick Coghlan wrote:
>
> Feature: Configuration API
> ==
>
> This change is proposed for inclusion in CPython 2.7.12 and later CPython
> 2.7.x
> releases. It consists of a new ``ssl._verify_https_certificates()`` to specify
> the default handl
Nick Coghlan writes:
> This is a significant rewrite that switches the PEP to a Standards
> Track PEP proposing two new features for 2.7.12+: an
> "ssl._verify_https_certificates()" configuration function, and a
> "PYTHONHTTPSVERIFY" environment variable (although writing them
> together like
