[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2019-04-14 Thread Terry J. Reedy
Terry J. Reedy added the comment: This issue is about the itemsize attribute of instances of the built-in memoryview class. Ctypes in only involved in providing format information. Hence the nosy additions. On Win10 with 3.8, ctypes has no uint attributes. Using 'c_int32' instead, I see

[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2018-09-06 Thread Eric Wieser
Eric Wieser added the comment: Pinging again, for lack of a clearer path forward -- ___ Python tracker ___ ___ Python-bugs-list

[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2018-07-08 Thread Eric Wieser
Eric Wieser added the comment: Pinging, as recommended by https://devguide.python.org/pullrequest/#reviewing. Ideally this and https://bugs.python.org/issue32780 would make the same patch release. -- ___ Python tracker

[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2018-02-09 Thread Terry J. Reedy
Change by Terry J. Reedy : -- nosy: +amaury.forgeotdarc, belopolsky, meador.inge ___ Python tracker ___

[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2018-02-06 Thread Eric Wieser
Change by Eric Wieser : -- keywords: +patch pull_requests: +5394 stage: -> patch review ___ Python tracker ___

[issue32782] ctypes: memoryview gives incorrect PEP3118 itemsize for array of length zero

2018-02-06 Thread Eric Wieser
New submission from Eric Wieser : Take the following simple structure: class Foo(ctypes.Structure): _fields_ = [('f', ctypes.uint32_t)] And construct some arrays with it: def get_array_view(N): return memoryview((Foo * N)()) In most cases,