8000 Fix typo in documentation (101 instead of 10). by adamlwgriffiths · Pull Request #423 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

Fix typo in documentation (101 instead of 10). #423

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

Merged
merged 1 commit into from
Sep 4, 2012
Merged

Fix typo in documentation (101 instead of 10). #423

merged 1 commit into from
Sep 4, 2012

Conversation

adamlwgriffiths
Copy link
Contributor

The example "Plot the function over [-10, 10]:" found at the following URL has a typo.
http://docs.scipy.org/doc/numpy/reference/generated/numpy.absolute.html

Examples demonstrate using an array with (-10, 0, 10),
but this specific example has a typo that lists the
last number as 101.
This is reflected in the diagrams having axis labeled
from -10:+10.

Examples demonstrate using an array with (-10, 0, 10),
but this specific example has a typo that lists the
last number as 101.
This is reflected in the diagrams having axis labeled
from -10:+10.
@travisbot
Copy link

This pull request fails (merged 0f1d2d9 into cd9092a).

@adamlwgriffiths
Copy link
Contributor Author

I'd appreciate if you could explain this to me how this commit has caused a build failure.
It's a simple 1-line documentation fix.

@njsmith
Copy link
Member
njsmith commented Sep 4, 2012

It doesn't seem to be your fault -- something's going wonky in the random tests, so it's probably some non-deterministic bug that your build happened to trip over... we don't even build the docs as part of the travisbot runs.

Which makes it very odd that all your builds failed the same way, if it's non-deterministic... I don't know what's going on :-(.

njsmith added a commit that referenced this pull request Sep 4, 2012
Fix typo in documentation (101 instead of 10).
@njsmith njsmith merged commit 4c73e7c into numpy:master Sep 4, 2012
@njsmith
Copy link
Member
njsmith commented Sep 4, 2012

^^ Might as well merge, though; if it somehow starts causing widespread test failures then at least they'll be widespread so we can debug them :-).

@adamlwgriffiths
Copy link
Contributor Author

I need to retract this pull.
I realised the third parameter is the number of divisions to divide the values into.
The 101, although a curious value, is correct in order to generate a high resolution figure.

My apologies. I will retract this web I get home.

Cheers,
Adam

On 04/09/2012, at 7:17 PM, njsmith notifications@github.com wrote:

^^ Might as well merge, though; if it somehow starts causing widespread test failures then at least they'll be widespread so we can debug them :-).


Reply to this email directly or view it on GitHub.

njsmith added a commit that referenced this pull request Sep 4, 2012
Revert PR #423 (which was based on a misunderstanding).
@njsmith
Copy link
Member
njsmith commented Sep 4, 2012

Doh of course. I went ahead and reverted it, and added kwargs so the next person along won't be confused: a72ce7e

@adamlwgriffiths
Copy link
Contributor Author

Fantastic! My thoughts exactly. Appreciate your prompt response and help. I won't have to rush home now =)

Cheers,
Adam

On 04/09/2012, at 7:38 PM, njsmith notifications@github.com wrote:

Doh of course. I went ahead and reverted it, and added kwargs so the next person along won't be confused: a72ce7e


Reply to this email directly or view it on GitHub.

@certik
Copy link
Contributor
certik commented Sep 4, 2012

The failure is caused by #424, so no worries.

teoliphant pushed a commit to ContinuumIO/numpy that referenced this pull request Sep 25, 2012
Revert PR numpy#423 (which was based on a misunderstanding).
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.

4 participants
0