Skip to content
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

Slightly unclear Python installation instruction (Linux) #290

Closed
mstimberg opened this issue Jan 25, 2016 · 6 comments
Closed

Slightly unclear Python installation instruction (Linux) #290

mstimberg opened this issue Jan 25, 2016 · 6 comments

Comments

@mstimberg
Copy link
Contributor

The installation instructions for Python (i.e. Anaconda) are a bit unclear for Linux, I think. The instructions currently are (paraphrased):

  1. ...
  2. ...
  3. Install Python 3 using all of the defaults.
  4. Open a terminal window
  5. type bash Anaconda- + TAB
  6. Press enter. ...

I find it a bit confusing that "step 3" is actually not about doing anything (if you'd follow the instruction literally, you'd be done after step 3 with an installed Anaconda distribution), but what should be done is explained in the three following steps. Could we maybe number the steps 4-6 as 3a-3c (although this seems to be annoyingly complicated in HTML: http://stackoverflow.com/questions/12325284/are-letter-number-combinations-in-html-lists-possible)? Alternatively, wrapping the steps 4-6 in <ul>...</ul> might be an easy solution, although it will make the column even smaller.

Another small thing: the current step number 5 assumes that after opening the terminal window, we are in the directory with the downloaded file. I guess on most Linux installations the download would by default rather end up in the Downloads directory.

@gvwilson
Copy link
Contributor

Is this still an issue?

@gvwilson gvwilson self-assigned this Jul 31, 2016
@mstimberg
Copy link
Contributor Author

Is this still an issue?

The Linux installation instructions for Linux have not changed since my report, so yes (assuming others agree that the points I raised are actually an issue, of course).

@gvwilson
Copy link
Contributor

Thanks - I'll try to push an update next week.

@gvwilson gvwilson removed their assignment Oct 4, 2016
@marwahaha
Copy link
Contributor

@mstimberg What would be the best way to write the instructions?

@rgaiacs
Copy link
Contributor

rgaiacs commented Feb 4, 2017

@mstimberg and @marwahaha Do you still have interest to work on this?

@mstimberg
Copy link
Contributor Author

Sorry for having being quiet so long, I'll try to re-write the instructions and open a PR.

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

No branches or pull requests

4 participants