On Dec 19, 2016, at 00:26, Larry Hastings wrote:
> Python 3.6.0 final just slipped by two weeks.
While it should not affect decisions about 3.5.3 and 3.4.6, so there's no
confusion: the 3.6.0 release date slipped one week, from 2016-12-16 to
2016-12-23. Of course, until the release happens, it
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and
3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle"
around the release. I expect a flood of adoption of 3.6, and people
switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it
just seemed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/18/2016 07:54 PM, Nick Coghlan wrote:
> On 18 December 2016 at 18:31, Serhiy Storchaka
> wrote:
>
>> Later I'm planning following changes:
>>
>> * Add the const qualifier to the result of functions that return
>> references to internal repres
On 18 December 2016 at 18:31, Serhiy Storchaka wrote:
> Later I'm planning following changes:
>
> * Add the const qualifier to the result of functions that return
> references to internal representation of immutable objects, like
> PyBytes_AS_STRING() or PyUnicode_DATA(). While CPython internally
Originally C API didn't use the const qualifier. Over few last years the
const qualifier was added to C API if that preserved backward
compatibility. For example input "char *" parameters were changed to
"const char *". This makes C API compatible with C++, eliminates C
compiler warnings, and h
