2.6.1 release cycle has begun
I have started the release cycle for 2.6.1, are there outstanding issues or soon-to-be-committed features I should wait for? Please help with the release notice, what have we done since 2.6.0 or at all? Any suggestions for names? https://bitbucket.org/pypy/pypy/src/release-2.6.x/pypy/doc/release-2.6.1.rst Matti
I want to fix OS X issues on vmprof. maybe will do it now now On Wed, Aug 19, 2015 at 8:36 PM, Matti Picus <matti.picus@gmail.com> wrote:
I have started the release cycle for 2.6.1, are there outstanding issues or soon-to-be-committed features I should wait for? Please help with the release notice, what have we done since 2.6.0 or at all? Any suggestions for names?
https://bitbucket.org/pypy/pypy/src/release-2.6.x/pypy/doc/release-2.6.1.rst
Matti _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
I fixed a few bugs, I will write a parser for vmmap tomorrow On Wed, Aug 19, 2015 at 9:02 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:
I want to fix OS X issues on vmprof. maybe will do it now now
On Wed, Aug 19, 2015 at 8:36 PM, Matti Picus <matti.picus@gmail.com> wrote:
I have started the release cycle for 2.6.1, are there outstanding issues or soon-to-be-committed features I should wait for? Please help with the release notice, what have we done since 2.6.0 or at all? Any suggestions for names?
https://bitbucket.org/pypy/pypy/src/release-2.6.x/pypy/doc/release-2.6.1.rst
Matti _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On Thu, Aug 20, 2015 at 9:31 PM, Matti Picus <matti.picus@gmail.com> wrote:
On 19/08/15 22:54, Maciej Fijalkowski wrote:
I fixed a few bugs, I will write a parser for vmmap tomorrow Maciej Fijalkowski
Will the vmmap parser be part of pypy, and if so are you requesting I wait with 2.6.1 until it is ready? Matti
I hope not, but it needs to be tested. When do you want to release it? I can look into OS X issues tomorrow
How is python 3.4 release coming?. On Fri, Aug 21, 2015 at 3:08 AM, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Thu, Aug 20, 2015 at 9:31 PM, Matti Picus <matti.picus@gmail.com> wrote:
On 19/08/15 22:54, Maciej Fijalkowski wrote:
I fixed a few bugs, I will write a parser for vmmap tomorrow Maciej Fijalkowski
Will the vmmap parser be part of pypy, and if so are you requesting I wait with 2.6.1 until it is ready? Matti
I hope not, but it needs to be tested. When do you want to release it? I can look into OS X issues tomorrow _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
ah i c On Fri, Aug 21, 2015 at 11:08 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:
I don't think so, our 3.x releases are usually done at different times
On Fri, Aug 21, 2015 at 4:07 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
Will there be any 3.x release included in this?
Hi Matti, On 19 August 2015 at 20:36, Matti Picus <matti.picus@gmail.com> wrote:
Please help with the release notice, what have we done since 2.6.0 or at all?
The stdlib is now 2.7.10 and cffi is 1.2. I think the most interesting change is int-float-list-strategy, at least in terms of explaining it: """Use a compact strategy for Python lists that mix integers and floats, at least if the integers fit inside 32 bits. These lists are now stored as an array of floats, like lists that contain only floats; the difference is that integers are stored as tagged NaNs. (This should have no visible effect! After ``lst = [42, 42.5]``, the value of ``lst[0]`` is still *not* the float ``42.0`` but the integer ``42``.)""" Maybe mention that numpy support is getting more and more complete, and vmprof support is improving. A bientôt, Armin.
On Wednesday, 19 August 2015 21:36:37 Matti Picus wrote:
I have started the release cycle for 2.6.1, are there outstanding issues or soon-to-be-committed features I should wait for?
Hi Matti, It would be great if the patch from issue #2107 could be committed. The patch has been compile tested an FreeBSD. After this patch has been committed FreeBSD will not need any patches to compile PyPy (from the Ports Collection) :-D. Regards
participants (5)
-
Armin Rigo -
David Naylor -
Maciej Fijalkowski -
Matti Picus -
Phyo Arkar