-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix integers being passed as length to quiver3d. #15195
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I added a test and explicitly set the dtype rather than relying on implicitly picking up the float. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but I pushed 2 commits.
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
this did not get backported for v3.1.2 or v3.1.3 but is included in v3.2.0, re milestoned to match that. |
But the backport of this PR didn't happen for 3.2.0 either? |
This got merged before we branched. The commit claims to be in the rcs |
Oh yes, I hadn't realized this was so old. It is there. |
PR Summary
closes #15186.
As it turns out there was a subtle difference between
linspace(0, length, num=2)
andnp.asarray([0, length])
: the former always returns a float array...PR Checklist