-
Notifications
You must be signed in to change notification settings - Fork 56
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
Refurbish installation instructions #682
Conversation
Also link extension list in handbook itself. This is the best one around.
Incorporating the latest wisdom and helpers. The principle idea is to go from specific to generic, in order to let readers with less expertise find working solutions more quickly, while not hiding alternatives with better system-integration potential for more experienced users.
Primarily to have its in-text references resolve in the PDF
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.
Thank you! This structures this section much better and with less duplication, and it adds quite a number of useful information, especially about the datalad installer! I have added comments with a few minor language/typo nitpicks.
docs/intro/installation.rst
Outdated
DataLad requires Python 3.6, or a more recent version, to be installed on | ||
your system. Python 2 is an outdated, in technical terms "deprecated", | ||
version of Python. Although it still exist as the default Python version on | ||
many systems, it is no longer maintained since 2020, and thus, most software | ||
has dropped support for Python 2. If you only run Python 2 on your system, | ||
most Python software, including DataLad, will be incompatible, and hence | ||
unusable, resulting in errors during installation and execution. | ||
|
||
The easiest way to verify that this is the case is to open a terminal and | ||
type :command:`python` to start a Python session:: | ||
|
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.
DataLad requires Python 3.6, or a more recent version, to be installed on | |
your system. Python 2 is an outdated, in technical terms "deprecated", | |
version of Python. Although it still exist as the default Python version on | |
many systems, it is no longer maintained since 2020, and thus, most software | |
has dropped support for Python 2. If you only run Python 2 on your system, | |
most Python software, including DataLad, will be incompatible, and hence | |
unusable, resulting in errors during installation and execution. | |
The easiest way to verify that this is the case is to open a terminal and | |
type :command:`python` to start a Python session:: | |
Python 2 is an outdated, in technical terms "deprecated", | |
version of Python. Although it still exist as the default Python version on | |
many systems, it is no longer maintained since 2020, and thus, most software | |
has dropped support for Python 2. If you only run Python 2 on your system, | |
most Python software, including DataLad, will be incompatible, and hence | |
unusable, resulting in errors during installation and execution. | |
DataLad requires Python 3.6, or a more recent version, to be installed on | |
your system. | |
The easiest way to verify that this is the case is to open a terminal and | |
type :command:`python` to start a Python session:: | |
How about moving the first sentence to the end of the paragraph? (looks like a large diff in the suggestion here, but I have just moved the sentence). I think this would connect the first paragraph better to the find-out-more header, the the next section on checking python versions to the requirement of Py 3.6 and higher.
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.
Good point! Maybe moving all of Python2 to the end is another approach -- this info will become less and less relevant over time.
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.
True. This is a good idea 👍
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 pushed an alternative.
Co-authored-by: Adina Wagner <adina.wagner@t-online.de>
in #682 (review) With the same overall goal: better connect version info and test. But move all PY2 info to the end, anticipating that it will get more and more irrelevant over time.
@yarikoptic @jwodder I will merge this now, to be able to continue in related work, but please leave your comments, if you see potential for better. Thx! |
Thx for the review @adswa ! |
Incorporating the latest wisdom and helpers.
The principle idea is to go from specific to generic, in order to let
readers with less expertise find working solutions more quickly, while
not hiding alternatives with better system-integration potential for
more experienced users.
Fixes #677
@yarikoptic @jwodder If you have advice on what to do differently, please let me know.