On 19.12.2016 06:26, Larry Hastings wrote:
>
>
> 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 mayb
On Mon, Dec 19, 2016 at 11:50 PM, Chris Barker
wrote:
> Please don't get rid of unicode+literals -- I don't even think we should
> depreciate it as a recommendation or discourage it.
>
> Maybe a note or two added as to where issues may arise would be good.
>
> I've found importing unicode_literal
For those who aren't aware, the stable API (PEP 384) is broken on
Windows because the exports from python3.dll have not been kept up to date.
Over at http://bugs.python.org/issue23903 we're trying to address this
by automatically generating the DLL based on the headers. This has shown
that man
I should also point out that when 3.6.0 releases, all of these will already be
in the stable API for other platforms. I'm not going to take a stance on
whether we can break it there between 3.6.0 and 3.6.1, but it may already be
too late to remove any.
Top-posted from my Windows Phone
-Ori
