PyPy 15.11 release is imminent
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:
I have started a major release cycle, and consensus was to start a new numbering scheme, based on yy.mm
While every release is a major event (yes 2.5.0, you can get a participation award too) this one really is a biggie. Warmup and tracing memory improvements, internal refactoring, SIMD vectorization on x86, and more.
Please let me know if there are more good things worth waiting for and help flesh out the release notice https://bitbucket.org/pypy/pypy/src/default/pypy/doc/release-15.11.0.rst
Matti
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
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:
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:
I have started a major release cycle, and consensus was to start a new numbering scheme, based on yy.mm
While every release is a major event (yes 2.5.0, you can get a participation award too) this one really is a biggie. Warmup and tracing memory improvements, internal refactoring, SIMD vectorization on x86, and more.
Please let me know if there are more good things worth waiting for and help flesh out the release notice https://bitbucket.org/pypy/pypy/src/default/pypy/doc/release-15.11.0.rst
Matti
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On 16/10/15 15:23, Phyo Arkar 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 ?
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
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:
On 16/10/15 15:23, Phyo Arkar 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 ?
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 _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
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:
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
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:
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:
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
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On 17/10/15 15:10, Phyo Arkar wrote:
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 <mailto:arigo@tunes.org>> 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
On Sat, Oct 17, 2015 at 11:57 AM, Armin Rigo <arigo@tunes.org> wrote:
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.
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.
On Sunday, 18 October 2015 08:34:43 anatoly techtonik wrote:
On Sat, Oct 17, 2015 at 11:57 AM, Armin Rigo <arigo@tunes.org> wrote:
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.
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.
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 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
On Mon, Oct 19, 2015 at 5:00 PM, Robin Becker <robin@reportlab.com> 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?
...... 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?
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.
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:
..........
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
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
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:
I have started a major release cycle, and consensus was to start a new numbering scheme, based on yy.mm
While every release is a major event (yes 2.5.0, you can get a participation award too) this one really is a biggie. Warmup and tracing memory improvements, internal refactoring, SIMD vectorization on x86, and more.
Please let me know if there are more good things worth waiting for and help flesh out the release notice https://bitbucket.org/pypy/pypy/src/default/pypy/doc/release-15.11.0.rst
Matti
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On 21/10/15 00:48, Antonio Cuni wrote:
why using yy.mm <http://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
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
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:
On 21/10/15 00:48, Antonio Cuni wrote:
why using yy.mm <http://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
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 _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On Wed, Oct 21, 2015 at 9:04 AM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
Just make a pypy that automatically compatible between python2 nd 3 and name it pyoy5 :P
I know it is not feasible.
Run two in parallel and kill the one that gives error first. -- anatoly t
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:
On 10/20/2015 19:09, 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 Matti
Oh thank goodness.
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
PyPy3 4.0.0 On 10/26/2015 02:47, Phyo Arkar wrote:
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 <mailto:tritium-list@sdamon.com>> wrote:
On 10/20/2015 19:09, 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 Matti
Oh thank goodness.
_______________________________________________ pypy-dev mailing list pypy-dev@python.org <mailto:pypy-dev@python.org> https://mail.python.org/mailman/listinfo/pypy-dev
yeah , that sounds weird. On Mon, Oct 26, 2015 at 1:18 PM, Alexander Walters <tritium-list@sdamon.com> wrote:
PyPy3 4.0.0
On 10/26/2015 02:47, Phyo Arkar wrote:
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:
On 10/20/2015 19:09, 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 Matti
Oh thank goodness.
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
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:
yeah , that sounds weird.
On Mon, Oct 26, 2015 at 1:18 PM, Alexander Walters <tritium-list@sdamon.com> wrote:
PyPy3 4.0.0
On 10/26/2015 02:47, Phyo Arkar wrote:
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:
On 10/20/2015 19:09, 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 Matti
Oh thank goodness.
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
participants (10)
-
Alexander Walters -
anatoly techtonik -
Antonio Cuni -
Armin Rigo -
David Naylor -
Maciej Fijalkowski -
Matti Picus -
Phyo Arkar -
Robin Becker -
Yury V. Zaytsev