Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1800
___
___
Lenard Lindstrom le...@telus.net added the comment:
I have checked over the proposed patch and made a small change that more
elegantly obtains PyCArrayType. Decaying arrays into pointers is not an ideal
solution. Ctypes arrays have bounds checking (pointers do not) adding an extra
margin of
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Anybody?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1800
___
___
Python-bugs-list
Lenard Lindstrom le...@telus.net added the comment:
I will check it out.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1800
___
___
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
--
nosy: +belopolsky
stage: - unit test needed
versions: +Python 3.2, Python 3.3 -Python 2.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1800
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
Attached patch fixes the issue, but feels a little bit like a band-aid. I think
making array arguments decay into pointers is the right solution, but I am
not sure this should be done when prototype is created or when it
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
--
keywords: +needs review
stage: unit test needed - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1800
___
New submission from Lenard Lindstrom:
When a callback is created with an array argument and then is called
from Python the callback function receives an array full of garbage.
Here is an example:
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit
(Intel)] on
win32
Type help,
Changes by Christian Heimes:
--
assignee: - theller
nosy: +theller
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1800
__
___
Python-bugs-list
