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
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
