Your assumption is correct. Perhaps the PEP 7 should be partitioned into
"< 3.6" and "3.6" sections where applicable.
On Mon, Jan 9, 2017, at 12:50, Brett Cannon wrote:
> https://bugs.python.org/issue29215 noticed that PEP 7 says "C++-style
> line
> comments" are allowed, but then later says "Neve
https://bugs.python.org/issue29215 noticed that PEP 7 says "C++-style line
comments" are allowed, but then later says "Never use C++ style // one-line
comments." I'm assuming we are sticking with allowing C++-style comments
and the "never" link just needs an addendum to say that only applies to
cod
> This list is for development of furture releases. Questions about using
> current releases should go to python-list, Stackoverflow, or other help
> forums.
The python-Mac SIG would be a good one for this.
CHB
>
> --
> Terry Jan Reedy
>
>
> ___
> P
> This is what happens with numpy arrays:
>
> >>> bytes(numpy.array([2], 'i1'))
> b'\x00\x00'
>
> >>> bytes(numpy.array([2, 2], 'i1'))
> b'\x02\x02'
>
> For better or worse, single-element numpy arrays have a working __index__
> methods
Ouch -- that probably is for the worse..
There are Numpy
On Mon, Jan 9, 2017 at 12:29 PM, Terry Reedy wrote:
> The tkinter doc still has
>
> ...to use Tkinter all you need is a simple import statement:
> import tkinter
> Or, more often:
> from tkinter import *
>
> Should this be changed?
>
yes, it should.
I would suggest suggesting something like