[Python-Dev] Benchmark results across all major Python implementations

On Monday, November 16, 2015, Brett Cannon > wrote: > > > On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > >> Hi Brett >> >> Any thoughts on improving the benchmark set (I think all of >>

[Python-Dev] Benchmark results across all major Python implementations

On Monday, November 16, 2015, Brett Cannon > wrote: > > > On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > >> Hi Brett >> >> Any thoughts on improving the benchmark set (I think all of >>

Re: [Python-Dev] Benchmark results across all major Python implementations

On Mon, Nov 16, 2015 at 3:38 PM, Brian Curtin wrote: > On Monday, November 16, 2015, Brett Cannon wrote: >>> >>> Hi Brett >>> >>> Any thoughts on improving the benchmark set (I think all of >>> {cpython,pypy,pyston} introduced new benchmarks to the set). >>

Re: [Python-Dev] Benchmark results across all major Python implementations

On 16/11/2015 22:23, Zachary Ware wrote: On Mon, Nov 16, 2015 at 3:38 PM, Brian Curtin wrote: On Monday, November 16, 2015, Brett Cannon wrote: Hi Brett Any thoughts on improving the benchmark set (I think all of {cpython,pypy,pyston} introduced new

Re: [Python-Dev] Benchmark results across all major Python implementations

On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > Hi Brett > > Any thoughts on improving the benchmark set (I think all of > {cpython,pypy,pyston} introduced new benchmarks to the set). > We should probably start a mailing list and finally hash out a common set of

[Python-Dev] Benchmark results across all major Python implementations

I gave the opening keynote at PyCon CA and then gave the same talk at PyData NYC on the various interpreters of Python (Jupyter notebook of my presentation can be found at bit.ly/pycon-ca-keynote; no video yet). I figured people here might find the benchmark numbers interesting so I'm sharing the

Re: [Python-Dev] Benchmark results across all major Python implementations

Hi Brett Any thoughts on improving the benchmark set (I think all of {cpython,pypy,pyston} introduced new benchmarks to the set). "speed.python.org" becoming a thing is generally stopped on "noone cares enough to set it up". Cheers, fijal On Mon, Nov 16, 2015 at 9:18 PM, Brett Cannon

Re: [Python-Dev] Benchmark results across all major Python implementations

On Mon, 16 Nov 2015 21:23:49 +0100, Maciej Fijalkowski wrote: > Any thoughts on improving the benchmark set (I think all of > {cpython,pypy,pyston} introduced new benchmarks to the set). > "speed.python.org" becoming a thing is generally stopped on "noone > cares enough to set

Re: [Python-Dev] Benchmark results across all major Python implementations

Last June we started publishing a daily performance report of the latest Python tip against the previous day's run and some established synch point. We mail these to the community to act as a "canary in the coal mine." I wrote about it at

Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

Hm, making Christian the BDFL-delegate would mean two out of three authors *and* the BDFL-delegate all working for Red Hat, which clearly has a stake (and IIUC has already committed to this approach ahead of PEP approval). SO then it would look like this is just rubber-stamping Red Hat's internal

Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

So I dropped the ball on this too -- I was going to either have a look or tell you quickly to find a BDFL-delegate, but ended up doing neither. Skimming it now I really don't think I'm the right person to review this. Maybe you could ask Alex Gaynor? On Tue, Nov 10, 2015 at 4:47 PM, Nick Coghlan

Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

On 17 November 2015 at 09:07, Guido van Rossum wrote: > So I dropped the ball on this too -- I was going to either have a look > or tell you quickly to find a BDFL-delegate, but ended up doing > neither. Skimming it now I really don't think I'm the right person to > review this.

Re: [Python-Dev] Reading Python source file

MRAB writes: > As I understand it, *nix expects the shebang to be b'#!', > which means that the first line should be ASCII-compatible > (it's possible that the UTF-8 BOM might be present). The UTF-8 BOM interferes with it on Mac OSX and Linux, at least.

Re: [Python-Dev] Benchmark results across all major Python implementations

Brett, Very cool, I'm glad to see that Jython's performance was competitive under most of these benchmarks. I would also be interested in joining the proposed mailing list. re elementtree - I assume the benchmarking is usually done with cElementTree. However Jython currently lacks a Java

Re: [Python-Dev] Reading Python source file

If you free the memory used for the source buffer before starting code generation you should be good. On Mon, Nov 16, 2015 at 5:53 PM, Serhiy Storchaka wrote: > I'm working on rewriting Python tokenizer (in particular the part that reads > and decodes Python source file).

Re: [Python-Dev] Reading Python source file

On 2015-11-17 01:53, Serhiy Storchaka wrote: I'm working on rewriting Python tokenizer (in particular the part that reads and decodes Python source file). The code is complicated. For now there are such cases: * Reading from the string in memory. * Interactive reading from the file. * Reading

[Python-Dev] Reading Python source file

I'm working on rewriting Python tokenizer (in particular the part that reads and decodes Python source file). The code is complicated. For now there are such cases: * Reading from the string in memory. * Interactive reading from the file. * Reading from the file: - Raw reading ignoring

Re: [Python-Dev] [Python-checkins] Daily reference leaks (97e2a6810f7f): sum=10

Just an FYI there seems to be a consistent, minor refcount leak found by test_capi that has been there for what seems like a couple of weeks. On Mon, 16 Nov 2015 at 00:42 wrote: > results for 97e2a6810f7f on branch "default" > >