Switching to 3.6 now and putting on my grumpy hat in case anger is really
needed.
On Tue, Dec 27, 2016 at 2:22 PM, Tomaz Muraus wrote:
> Sounds good to me :)
>
> On Dec 27, 2016 9:33 PM, "anthony shaw" wrote:
>
> I just merged a PR to add Python 3.6.0 to the build, now that it's
> released. The
Sounds good to me :)
On Dec 27, 2016 9:33 PM, "anthony shaw" wrote:
I just merged a PR to add Python 3.6.0 to the build, now that it's
released. The build failed the first time, the function spec of showwarning
in the warnings.py changed, but we only used it within a test module so I
would say i
Yes please!
On Tue, Dec 27, 2016, 21:33 anthony shaw wrote:
> I just merged a PR to add Python 3.6.0 to the build, now that it's
> released. The build failed the first time, the function spec of showwarning
> in the warnings.py changed, but we only used it within a test module so I
> would say i
I just merged a PR to add Python 3.6.0 to the build, now that it's released.
The build failed the first time, the function spec of showwarning in the
warnings.py changed, but we only used it within a test module so I would say it
works fine in 1.5.0 release bits
We can say that 3.6 is experiment
