8000 Broken Link on Bleeding Edge installation instructions web page · Issue #7586 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

Broken Link on Bleeding Edge installation instructions web page #7586

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

Closed
elliott2081 opened this issue Oct 5, 2016 · 2 comments · Fixed by #7592
Closed

Broken Link on Bleeding Edge installation instructions web page #7586

elliott2081 opened this issue Oct 5, 2016 · 2 comments · Fixed by #7592
Labels
Documentation Easy Well-defined and straightforward way to resolve

Comments

@elliott2081
Copy link
Contributor

Description

In the bleeding-edge installation instructions there is a link to the Nose testing package.

https://somethingaboutorange.com/mrl/projects/nose/

but that page appears to be missing possibly permantly. I think it should be this -> http://nose.readthedocs.io/en/latest/

the original page on sci-kit.org is here -
http://scikit-learn.org/stable/developers/advanced_installation.html#install-bleeding-edge

Steps/Code to Reproduce

Expected Results

Actual Results

Versions

@nelson-liu
Copy link
Contributor

Could you help us open a PR to fix this ?

@jnothman jnothman added Easy Well-defined and straightforward way to resolve Documentation Need Contributor labels Oct 6, 2016
@elliott2081
Copy link
Contributor Author

I did. As I noted in the PR, this has been fixed before. I can't find a commit that reversed the change. But the current branch code definitely is using the broken link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Easy Well-defined and straightforward way to resolve
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
0