This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author twouters
Recipients theller, twouters
Date 2007-08-29.21:26:28
SpamBayes Score 0.03139173
Marked as misclassified No
Message-id <1188422788.97.0.84131387766.issue1617699@psf.upfronthosting.co.za>
In-reply-to
Content
Implemented actual extended slicing support for the Array and Pointer
types. The semantics of negative and ommitted indices in the Pointer
case are somewhat muddy, but I took the approach the simple slicing code
took: pretend the programmer knows what they're doing, and that the
'sequence' that is the pointer is actually PY_SSIZE_T_MAX elements long.
I'm not sure I like that approach at all, but the actual problem is the
unbounded nature of the pointers, and this is the only approach I can
think of that makes sense, short of completely disallowing negative or
missing indices.

This patch is pretty much done now, I think. Note that it's entirely
backward compatible, the incompatible bits (removing simple slicing)
happen in Py3K.
Files
File name Uploaded
noslice.ctypes.diff twouters, 2007-08-29.21:26:28
History
Date User Action Args
2007-08-29 21:26:29twouterssetspambayes_score: 0.0313917 -> 0.03139173
recipients: + twouters, theller
2007-08-29 21:26:28twouterssetspambayes_score: 0.0313917 -> 0.0313917
messageid: <1188422788.97.0.84131387766.issue1617699@psf.upfronthosting.co.za>
2007-08-29 21:26:28twouterslinkissue1617699 messages
2007-08-29 21:26:28twouterscreate