On behalf of the Python development community and the Python 3.6 release
team, I'm excited to announce the availability of Python 3.6.0rc1. 3.6.0rc1
is the release candiate for Python 3.6, the next major release of
Python.
Code for 3.6.0 is now frozen. Assuming no release critical problems are
fo
> and I also don’t see any clue in the source as to when [list mutation]
> would actually happen. Since inside the loop, the list object `v` is
> never accessed other than passing `v->ob_item[i]` to the recursive
> repr call, there shouldn’t be any mutation on the list object itself.
The individu
On Tue, Dec 6, 2016, at 05:27, Patrick Westerhoff wrote:
> Hey all,
>
> I just stumbled on the following comment in the C source of the repr
> implementation for the list object:
>
> /* Do repr() on each element. Note that this may mutate the list,
>so must refetch the list size on ea
Hey all,
I just stumbled on the following comment in the C source of the repr
implementation for the list object:
/* Do repr() on each element. Note that this may mutate the list,
so must refetch the list size on each iteration. */
(as seen in list_repr implementation [1])
I’m honest
Hi Nick,
On 5 December 2016 at 13:22, Nick Coghlan wrote:
> I think 3 omnibus issues would be a reasonable way to go, with the
> discussion on those issues then splitting things out to either new
> issue reports, or entries in
> https://hg.python.org/cpython/file/default/Lib/test/crashers/ (if an
Hi Raymond,
On 6 December 2016 at 05:59, Raymond Hettinger
wrote:
> Also, we use {...} instead of OrderedDict(...).
No, at least CPython 3.5.2 uses ``...`` for OrderedDict, and not
``{...}``. Following that example, deques should also use ``...``
instead of ``[...]``. But I bow to your choice
