Re: [Python-Dev] re performance

Regarding to the performance difference between "re" and "regex" and packaging related options, we did a performance comparison using Python 3.6.0 to run some micro-benchmarks in the Python Benchmark Suite (https://github.com/python/performance): Results in ms, and the lower the better

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

On 30Jan2017 1310, Christian Heimes wrote: On 2017-01-30 21:50, Cory Benfield wrote: On 30 Jan 2017, at 13:53, David Cournapeau wrote: Are there any official recommendations for downstream packagers beyond PEP 476 ? Is it "acceptable" for downstream packagers to patch

[Python-Dev] Heads up: possible double-comments on bpo for commits

I've activated the webhook for receiving comments on issues when a commit lands mentioning an issue, so if you see a commit from our hg integration and another from GitHub, understand that's why (mention issues as "bpo " in commit messages if you want to see it in action). If it becomes too

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

On 31 January 2017 at 14:54, Cory Benfield wrote: > > So C# applications are Windows-native safe on Windows, and are a crapshoot > elsewhere. For Java vs Python, I’d say we’re slightly ahead right now. That's precisely the sort of answer I was after. Many thanks. The

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

> On 31 Jan 2017, at 09:56, Paul Moore wrote: > > On 31 January 2017 at 09:19, Cory Benfield wrote: >> >> In general, it is unwise to mix trust stores. If you want to use your OS’s >> trust store, the best approach is to use the OS’s TLS stack as well.

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

On Tue, Jan 31, 2017 at 9:19 AM, Cory Benfield wrote: > > On 30 Jan 2017, at 21:00, David Cournapeau wrote: > > > > On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield wrote: > >> >> >> > On 30 Jan 2017, at 13:53, David Cournapeau

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

On 31 January 2017 at 09:19, Cory Benfield wrote: > > In general, it is unwise to mix trust stores. If you want to use your OS’s > trust store, the best approach is to use the OS’s TLS stack as well. At > least that way when a user says “It works in my browser”, you know it

Re: [Python-Dev] re performance

On 30 January 2017 at 15:26, Barry Warsaw wrote: > On Jan 30, 2017, at 12:38 PM, Nick Coghlan wrote: > >>I think there are 3 main candidates that could fit that bill: >> >>- requests >>- setuptools >>- regex > > Actually, I think pkg_resources would make an excellent candidate.

Re: [Python-Dev] Generator objects and list comprehensions?

On 30 January 2017 at 19:05, Brett Cannon wrote: > On Sun, 29 Jan 2017 at 16:39 Craig Rodrigues wrote: >> I'm OK with either approach. Leaving things the way they are in Python 3 >> is no good, IMHO. > > My vote is it be a SyntaxError since you're not

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

> On 31 Jan 2017, at 09:33, Christian Heimes wrote: > > One small correction, it is possible to export some of the trust > settings to a TRUSTED CERTIFICATE and import them into OpenSSL. It works > correctly in 1.0.1 and since 1.0.2e or f. Trust settings are stored in >

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

On 2017-01-31 10:19, Cory Benfield wrote: > >> On 30 Jan 2017, at 21:00, David Cournapeau > > wrote: >> >> >> >> On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield > > wrote: >> >> >> >> > On 30 Jan

Re: [Python-Dev] SSL certificates recommendations for downstream python packagers

> On 30 Jan 2017, at 21:00, David Cournapeau wrote: > > > > On Mon, Jan 30, 2017 at 8:50 PM, Cory Benfield > wrote: > > > > On 30 Jan 2017, at 13:53, David Cournapeau > >