Skip to content

Fix stride_stricks.as_strided function for object arrays - #4408

Merged
juliantaylor merged 1 commit into
numpy:maintenance/1.8.xfrom
charris:backport-1.8-gh-4377
Mar 1, 2014
Merged

juliantaylor merged 1 commit into
numpy:maintenance/1.8.xfrom
charris:backport-1.8-gh-4377

Conversation

@charris

@charris charris commented Mar 1, 2014

Copy link
Copy Markdown
Member

Currently, calling as_strided for object array results in 'TypeError: Cannot change data-type for object array.'. Fix so that dtype of new array is only set for void dtype, as originally intended.

Currently, calling as_strided for object array results in 'TypeError: Cannot change data-type for object array.'. Fix so that dtype of new array is only set for void dtype, as originally intended.
@juliantaylor

Copy link
Copy Markdown
Contributor

I'm going to assume you picked the right PR to merge :)
merging pending travis

anything still missing? I wanted to start the windows builds now.

@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

@juliantaylor I hope so too ;) There was still a bug in the other and my main reservation here was not noticing kind was used, not char. That user types are classified as 'V' kind was new to me. I wonder how endianess gets handled, if at all.

juliantaylor added a commit that referenced this pull request Mar 1, 2014
Fix stride_stricks.as_strided function for object arrays
@juliantaylor
juliantaylor merged commit 5e313b7 into numpy:maintenance/1.8.x Mar 1, 2014
@charris
charris deleted the backport-1.8-gh-4377 branch March 1, 2014 17:07
@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

What about #4146?

@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

Documentation still needs an update for this one.

@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

NVM, this one didn't have an issue.

@juliantaylor

Copy link
Copy Markdown
Contributor

I don't have the concentration left to backport 4146 properly today, so either we skip it, add it post rc or delay rc until someone does it.

@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

I can sympathize with code burnout :0 If the backport is complicated, let's skip it. I get the impression you already made a quick pass at it.

I was planning on making the branch tomorrow, would you prefer today?

@juliantaylor

Copy link
Copy Markdown
Contributor

I guess I can wait until tomorrow

@charris

charris commented Mar 1, 2014

Copy link
Copy Markdown
Member Author

OK, I'll do it tomorrow, or maybe this evening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants