Mailman 3 PyPy 15.11 release is imminent - pypy-dev

newer
Diploma Thesis on Pypy

PyPy 15.11 release is imminent

older
Any Release incoming for pypy 3.x?

Matti Picus

Oct. 16, 2015

7:12 a.m.

Attachments:

attachment.html (text/html — 1.0 KB)

Show replies by date

Phyo Arkar

October 2015

2:21 p.m.

So that will work like 15.11 , 15.5 ? something like that? Predefined release cycle ? And Awesome work Guys!@ On Fri, Oct 16, 2015 at 11:42 AM, Matti Picus <matti.picus@gmail.com> wrote:

...

warmup time improvement of 20% or so at the cost of a minor regression in jitted code speed. 20% Warmup is huge! That will skyrocket in bencmarks. But Minor regression? how minor ? On Fri, Oct 16, 2015 at 6:51 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Matti Picus

2:33 p.m.

On 16/10/15 15:23, Phyo Arkar wrote:

...

speed.pypy.org (which measures only jit performance without warmup) went from 7.10 to 6.90, but of course that is just for those benchmarks Matti

Maciej Fijalkowski

3:31 p.m.

I claim at least a part of the jitted code change is a fluke. A part is due to disabling of retracing, which never worked properly as far as I know anyway, we'll reenable that somehow at some point. I would not put it in the release announcement. On Fri, Oct 16, 2015 at 2:33 PM, Matti Picus <matti.picus@gmail.com> wrote:

...

Armin Rigo

10:57 a.m.

Hi Phyo, On Fri, Oct 16, 2015 at 2:21 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

So that will work like 15.11 , 15.5 ? something like that? Predefined release cycle ?

No, you're jumping to conclusions only because of numbers that look like Ubuntu's. Armin

Phyo Arkar

2:10 p.m.

Lol I C. I was thinking that way. How abt also adding code names? I can come up with fun ones. On Oct 17, 2015 3:28 PM, "Armin Rigo" <arigo@tunes.org> wrote:

...

Maciej Fijalkowski

3:25 p.m.

We usually have code names, they just don't follow ANY known pattern On Sat, Oct 17, 2015 at 2:10 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Matti Picus

6:02 p.m.

On 17/10/15 15:10, Phyo Arkar wrote:

...

I kind of gave up with code names, it was a bit irrelevant and no-one used it after the release. But if someone has a good one, I am listening Matti

anatoly techtonik

7:34 a.m.

On Sat, Oct 17, 2015 at 11:57 AM, Armin Rigo <arigo@tunes.org> wrote:

...

I don't see the reason then. You can't jump back to plain versions. I used to do this versioning, but then realized that if I do major API break or just commit something huge, nobody will get the idea. -- anatoly t.

David Naylor

12:15 p.m.

On Sunday, 18 October 2015 08:34:43 anatoly techtonik wrote:

...

I agree, I prefer to use semantic versioning (see http://semver.org/). Not sure if it is too late but has this been considered, and rejected?

Robin Becker

4 p.m.

..........

...

I agree, I prefer to use semantic versioning (see http://semver.org/). Not sure if it is too late but has this been considered, and rejected?

...... I think the intention is just year:month, but how does this relate to the python version semantics ie does 15.11 support 2.7 only? -- Robin Becker

anatoly techtonik

4:07 p.m.

On Mon, Oct 19, 2015 at 5:00 PM, Robin Becker <robin@reportlab.com> wrote:

...

FWIW, the final format that I chose became 1.YY.M 1 - is the API version or whatever YY.M - is an obvious indicator of the freshness of the package -- anatoly t.

Maciej Fijalkowski

4:38 p.m.

Yes, PyPy, whatever version, will support python 2.7 for the forseeable future. PyPy3 whatever version will support 3.x On Mon, Oct 19, 2015 at 4:00 PM, Robin Becker <robin@reportlab.com> wrote:

...

Antonio Cuni

3:48 p.m.

why using yy.mm instead of just a single increasing int number like Chrome? To avoid confusions, we should probably skip pypy 3 and start releasing from pypy 4. It looks just simpler than 15.11 and friends to me. ciao, Anto On Fri, Oct 16, 2015 at 7:12 AM, Matti Picus <matti.picus@gmail.com> wrote:

...

Matti Picus

1:09 a.m.

On 21/10/15 00:48, Antonio Cuni wrote:

...

After a short discussion on IRC, it turns out this is the popular view, so the next release wll be called PyPy 4.0.0 Matti

Yury V. Zaytsev

7:38 a.m.

On Wed, 2015-10-21 at 10:09 +1100, Matti Picus wrote:

...

After a short discussion on IRC, it turns out this is the popular view, so the next release wll be called PyPy 4.0.0

Yay! I also think that it's a great(er) idea ;-) -- Sincerely yours, Yury V. Zaytsev

Phyo Arkar

8:04 a.m.

Just make a pypy that automatically compatible between python2 nd 3 and name it pyoy5 :P I know it is not feasible. On Wed, Oct 21, 2015, 5:40 AM Matti Picus <matti.picus@gmail.com> wrote:

...

anatoly techtonik

9:19 a.m.

On Wed, Oct 21, 2015 at 9:04 AM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Run two in parallel and kill the one that gives error first. -- anatoly t

Alexander Walters

12:25 a.m.

On 10/20/2015 19:09, Matti Picus wrote:

...

Phyo Arkar

7:47 a.m.

PyPy 4.0.0 sounds a lot better but how we will name newer versions of PyPy3 ? On Sun, Oct 25, 2015 at 4:55 AM, Alexander Walters <tritium-list@sdamon.com> wrote:

...

Alexander Walters

7:48 a.m.

PyPy3 4.0.0 On 10/26/2015 02:47, Phyo Arkar wrote:

...

Phyo Arkar

7:50 a.m.

yeah , that sounds weird. On Mon, Oct 26, 2015 at 1:18 PM, Alexander Walters <tritium-list@sdamon.com> wrote:

...

Maciej Fijalkowski

9:25 a.m.

The problem is that everything sounds weird and pypy3 4.0 sounds less weird than other options On Mon, Oct 26, 2015 at 7:50 AM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Phyo Arkar

October 2015

12:21 p.m.

So that will work like 15.11 , 15.5 ? something like that? Predefined release cycle ? And Awesome work Guys!@ On Fri, Oct 16, 2015 at 11:42 AM, Matti Picus <matti.picus@gmail.com> wrote:

...

Phyo Arkar

12:23 p.m.

...

Matti Picus

12:33 p.m.

On 16/10/15 15:23, Phyo Arkar wrote:

...

speed.pypy.org (which measures only jit performance without warmup) went from 7.10 to 6.90, but of course that is just for those benchmarks Matti

Maciej Fijalkowski

1:31 p.m.

...

Armin Rigo

8:57 a.m.

Hi Phyo, On Fri, Oct 16, 2015 at 2:21 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

So that will work like 15.11 , 15.5 ? something like that? Predefined release cycle ?

No, you're jumping to conclusions only because of numbers that look like Ubuntu's. Armin

Phyo Arkar

12:10 p.m.

Lol I C. I was thinking that way. How abt also adding code names? I can come up with fun ones. On Oct 17, 2015 3:28 PM, "Armin Rigo" <arigo@tunes.org> wrote:

...

Maciej Fijalkowski

October 2015

1:25 p.m.

We usually have code names, they just don't follow ANY known pattern On Sat, Oct 17, 2015 at 2:10 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Matti Picus

4:02 p.m.

On 17/10/15 15:10, Phyo Arkar wrote:

...

I kind of gave up with code names, it was a bit irrelevant and no-one used it after the release. But if someone has a good one, I am listening Matti

anatoly techtonik

5:34 a.m.

On Sat, Oct 17, 2015 at 11:57 AM, Armin Rigo <arigo@tunes.org> wrote:

...

David Naylor

10:15 a.m.

On Sunday, 18 October 2015 08:34:43 anatoly techtonik wrote:

...

I agree, I prefer to use semantic versioning (see http://semver.org/). Not sure if it is too late but has this been considered, and rejected?

Robin Becker

2 p.m.

..........

...

I agree, I prefer to use semantic versioning (see http://semver.org/). Not sure if it is too late but has this been considered, and rejected?

...... I think the intention is just year:month, but how does this relate to the python version semantics ie does 15.11 support 2.7 only? -- Robin Becker

anatoly techtonik

2:07 p.m.

On Mon, Oct 19, 2015 at 5:00 PM, Robin Becker <robin@reportlab.com> wrote:

...

FWIW, the final format that I chose became 1.YY.M 1 - is the API version or whatever YY.M - is an obvious indicator of the freshness of the package -- anatoly t.

Maciej Fijalkowski

October 2015

4:38 p.m.

Yes, PyPy, whatever version, will support python 2.7 for the forseeable future. PyPy3 whatever version will support 3.x On Mon, Oct 19, 2015 at 4:00 PM, Robin Becker <robin@reportlab.com> wrote:

...

Antonio Cuni

3:48 p.m.

...

Matti Picus

1:09 a.m.

On 21/10/15 00:48, Antonio Cuni wrote:

...

After a short discussion on IRC, it turns out this is the popular view, so the next release wll be called PyPy 4.0.0 Matti

Yury V. Zaytsev

7:38 a.m.

On Wed, 2015-10-21 at 10:09 +1100, Matti Picus wrote:

...

After a short discussion on IRC, it turns out this is the popular view, so the next release wll be called PyPy 4.0.0

Yay! I also think that it's a great(er) idea ;-) -- Sincerely yours, Yury V. Zaytsev

Phyo Arkar

8:04 a.m.

Just make a pypy that automatically compatible between python2 nd 3 and name it pyoy5 :P I know it is not feasible. On Wed, Oct 21, 2015, 5:40 AM Matti Picus <matti.picus@gmail.com> wrote:

...

anatoly techtonik

9:19 a.m.

On Wed, Oct 21, 2015 at 9:04 AM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Run two in parallel and kill the one that gives error first. -- anatoly t

Alexander Walters

October 2015

10:25 p.m.

On 10/20/2015 19:09, Matti Picus wrote:

...

Phyo Arkar

6:47 a.m.

PyPy 4.0.0 sounds a lot better but how we will name newer versions of PyPy3 ? On Sun, Oct 25, 2015 at 4:55 AM, Alexander Walters <tritium-list@sdamon.com> wrote:

...

Alexander Walters

6:48 a.m.

PyPy3 4.0.0 On 10/26/2015 02:47, Phyo Arkar wrote:

...

Phyo Arkar

6:50 a.m.

yeah , that sounds weird. On Mon, Oct 26, 2015 at 1:18 PM, Alexander Walters <tritium-list@sdamon.com> wrote:

...

Maciej Fijalkowski

8:25 a.m.

The problem is that everything sounds weird and pypy3 4.0 sounds less weird than other options On Mon, Oct 26, 2015 at 7:50 AM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

3431

Age (days ago)

3442

Last active (days ago)

List overview

Download

23 comments

10 participants

participants (10)

Alexander Walters
anatoly techtonik
Antonio Cuni
Armin Rigo
David Naylor
Maciej Fijalkowski
Matti Picus
Phyo Arkar
Robin Becker
Yury V. Zaytsev

PyPy 15.11 release is imminent

tags

participants (10)