From: Patrick M. <pat...@gm...> - 2012-10-29 15:22:43
|
Just a follow up for historical sake: This is a bug in numpy and was introduced in this commit: https://github.com/numpy/numpy/commit/c48156dfdc408f0a1e59ef54ac490cccbd6b8d73 I've filed a ticket with Numpy and those interested can follow up here: https://github.com/numpy/numpy/issues/2700 PTM --- Patrick Marsh Ph.D. Candidate / Liaison to the HWT School of Meteorology / University of Oklahoma Cooperative Institute for Mesoscale Meteorological Studies National Severe Storms Laboratory http://www.patricktmarsh.com On Mon, Oct 29, 2012 at 8:46 AM, Benjamin Root <ben...@ou...> wrote: > > > On Mon, Oct 29, 2012 at 9:16 AM, Benjamin Root <ben...@ou...> wrote: > >> >> >> On Mon, Oct 29, 2012 at 1:51 AM, Patrick Marsh <pat...@gm...>wrote: >> >>> Greetings, >>> >>> I've banged my head against this problem for 2 days and have given up on >>> figuring it out on my own… >>> >>> After updating numpy and matplotlib to the latest versions from github >>> Saturday morning, I keep getting "AttributeError: incompatible shape for a >>> non-contiguous array" errors all over the place when plotting. When I run >>> tests on numpy, everything passes. When I run tests on matplotlib, I get 51 >>> errors, with a vast majority of them (possibly all) being the >>> non-contiguous array errors. (Sample below) >>> >>> Any suggestions here? I'm totally stumped. >>> >>> >>> PTM >>> >>> >>> >> I am guessing this is a problem introduced with NumPy. I just tried the >> tests with an older NumPy branch, and all seemed fine. Now testing with >> the most recent branch. >> >> Ben Root >> > > Confirming the bug (and it appears to be happening at a spot that I > updated a couple years ago to catch exactly these sort of situations where > reshaping would result in a copy when we didn't want a copy). > > I am presuming that it is a NumPy bug and will report it as such to the > numpy list. > > Cheers! > Ben Root > > |