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 chuck
Recipients barry, chuck, exarkun, georg.brandl, gregory.p.smith, ivank, loewis, pitrou
Date 2009-09-29.17:57:10
SpamBayes Score 3.637548e-10
Marked as misclassified No
Message-id <>
I was looking at the remaining differences between Modules/arraymodule.c 
in python 2.7 and the 3k branch, in particular I was testing why 
including the changes to the function array_ass_slice into the patch 
breaks the unit test of the array module.

The manual resizing of the memory basically was replaced by a call to 
array_resize with the advantage, that checking for exported memory views 
is done there (which is not necessary because it's already done in the 
function) and the code gets clearer. I think when PyMem_RESIZE is called 
the pointer to the memory might change. So in 3k this now happens in 
array_resize, so the array->ob_item pointer changes but not it's local 
copy in array_ass_slice. Isn't that potentially causing trouble in 
python 3k?
Date User Action Args
2009-09-29 17:57:12chucksetrecipients: + chuck, loewis, barry, georg.brandl, gregory.p.smith, exarkun, pitrou, ivank
2009-09-29 17:57:12chucksetmessageid: <>
2009-09-29 17:57:10chucklinkissue6071 messages
2009-09-29 17:57:10chuckcreate