-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Add Installation section in docs overview #7027
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
hmm, i'd personally prefer installation to be to the right of "Quick Start" (then shift everything to the right or down to the leftmost column of the new row) as opposed to all the way at the bottom |
of scikit-learn | ||
</blockquote> | ||
</div> | ||
|
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.
extraneous newline that was not there before
agree about the positioning. Can you please post a screenshot of the result? |
@nelson-liu Thanks for the comments on the PR. I will look into positioning the Installation link |
@souravsingh Hey, are you still working on this one ? |
@manu-chroma The PR is still open. I am working on updating it |
@souravsingh did you have a chance to get to this? |
@nelson-liu I am working on the issue now |
Only slightly related: we should link to winpython, https://winpython.github.io/, instead of Python(x,y) on the install page. Indeed, winpython is more maintained and more reactive these days (part of the developers of Python(x,y) moved to winpython). @souravsingh : do you think that you can do that? |
@GaelVaroquaux Sure, I can do it |
@amueller I have made modifications to the documentation link. Here is the screenshot- I am not able to figure out the problem with the last two links. Any help would be appreciated! |
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.
The issue looks like it stems from your use of <div class="row-fluid">
, which should be used once to encapsulate the 3 boxes that should be in a row. Here's how the document should be laid out:
<div class="row-fluid">
<!-- one row -->
<div class="span4 box">
<!-- one box (1st col)-->
</div>
<div class="span4 box">
<!-- one box (2nd col)-->
</div>
<div class="span4 box">
<!-- one box (3rd col)-->
</div>
</div>
@@ -39,14 +38,23 @@ Documentation of scikit-learn 0.18.dev0 | |||
</div> | |||
|
|||
<!-- row --> | |||
<div class="row-fluid"> | |||
<div class="row-fluid"> |
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.
this indentation is off from the original file
to apply them. | ||
</blockquote> | ||
</div> | ||
<div class="row-fluid"> |
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.
i believe you dont want this tag here, because it isn't in a separate row
<div class="span4 box"> | ||
<h2><a href="tutorial/index.html">Tutorials</a></h2> | ||
<blockquote>Useful tutorials for developing a feel | ||
for some of scikit-learn's applications in the | ||
machine learning field. | ||
</blockquote> | ||
</div> | ||
<div class="row-fluid"> |
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.
same as above
@@ -55,11 +63,7 @@ Documentation of scikit-learn 0.18.dev0 | |||
</blockquote> | |||
</div> | |||
|
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.
you want to end one of the rows here (every 3 span4 box
divs)
<blockquote>Frequently asked questions about the project and contributing. | ||
</blockquote> | ||
<h2><a href="presentations.html">Additional Resources</a></h2> | ||
<blockquote>Talks given, slide-sets and other information relevant to scikit-learn. |
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.
indentation
@nelson-liu Thanks for the review. Apart from the comments, Is there a problem in the positioning of the links? |
maybe move "additional resources" to the end, seeing as they are additional anyway. No strong opinion on that though, cosmetically it looks good as it is (excepting the alignment / row issues, of course). |
I have no idea what's happening with the pep8 check here :-/ @lesteve ? |
It seems like the common ancestor between the PR branch and master is a commit in February 2016, not sure why ... |
I guess that the problem can be fixed by a rebase on master. @souravsingh started working on this 3 months ago and at the time |
thanks for investigating @lesteve |
(Just do double check, the CI is run just on the PR, not on the PR merged into master, right?) |
That was the indea indeed, so that the lines reported by flake8 match with what the PR author has locally. |
which fixes the issue seen in scikit-learn#7027. Enhancements: * the script works on PRs targetting a fork rather than the reference repo * improved logic about when to unshallow the repo * fetching the upstream master branch into a reference rather than a branch (less intrusive for scripts than may run afterwards e.g. the ones in the after_success step) * Better logging messages
which fixes the issue seen in #7027. Enhancements: * the script works on PRs targetting a fork rather than the reference repo * improved logic about when to unshallow the repo * fetching the upstream master branch into a reference rather than a branch (less intrusive for scripts than may run afterwards e.g. the ones in the after_success step) * Better logging messages
I merged #7575 and restarted the Travis flake8 build, that should get Travis green. |
Restarted the CircleCI build without cache manually since it seems to have fixed a similar issue in another PR. |
@souravsingh Are you still working on this? |
My bad, I had forgotten about this. I will update the PR |
I mistakenly deleted the branch for the PR. I will send a PR again. |
which fixes the issue seen in scikit-learn#7027. Enhancements: * the script works on PRs targetting a fork rather than the reference repo * improved logic about when to unshallow the repo * fetching the upstream master branch into a reference rather than a branch (less intrusive for scripts than may run afterwards e.g. the ones in the after_success step) * Better logging messages
which fixes the issue seen in scikit-learn#7027. Enhancements: * the script works on PRs targetting a fork rather than the reference repo * improved logic about when to unshallow the repo * fetching the upstream master branch into a reference rather than a branch (less intrusive for scripts than may run afterwards e.g. the ones in the after_success step) * Better logging messages
which fixes the issue seen in scikit-learn/scikit-learn#7027. Enhancements: * the script works on PRs targetting a fork rather than the reference repo * improved logic about when to unshallow the repo * fetching the upstream master branch into a reference rather than a branch (less intrusive for scripts than may run afterwards e.g. the ones in the after_success step) * Better logging messages
Reference Issue
Fixes #7023 for adding an installation link on the documentation
What does this implement/fix? Explain your changes.
Adds a link to Installation on the overview page.