Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

BUG: fix not returning out array from ufuncs with subok=False set#5242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
charris merged 1 commit intonumpy:masterfromjuliantaylor:fix-ufunc-subok-out
Oct 28, 2014

Conversation

@juliantaylor
Copy link
Contributor

closesgh-5240

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Umm, wrap what? Why put None into the out argument slots?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

None is the value used to indicate to return the output argument NULL is create a new return array viaPyArray_Return

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

OK, might add that to the comment.

@charris
Copy link
Member

Thanks Julian. I needed a PR I could commit ;)

charris added a commit that referenced this pull requestOct 28, 2014
BUG: fix not returning out array from ufuncs with subok=False set
@charrischarris merged commit3b22d87 intonumpy:masterOct 28, 2014
juliantaylor added a commit that referenced this pull requestOct 28, 2014
BUG: fix not returning out array from ufuncs with subok=False set
@juliantaylorjuliantaylor deleted the fix-ufunc-subok-out branchOctober 28, 2014 23:15
@mhvk
Copy link
Contributor

Thanks for solving it so quickly. Just in case: Since you had milestone 1.9.1 for#5240, should it be set here as well, as a reminder to add it to that branch?

@juliantaylor
Copy link
ContributorAuthor

I have already pushed the commit to the branch

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

BUG np.std with output given stores variance in output

3 participants

@juliantaylor@charris@mhvk

[8]ページ先頭

©2009-2025 Movatter.jp