Printing all results in a cell | Removed possible unintended texts | Corrected typos | Report broken hyperlinks in binder (see below) #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Corrected typos | Report broken hyperlinks in binder (see description)
Fixed a typo on line 1071. Actual number in the text should have been 100.
Fixed typo in line 43: "here" into "hear" P.S. Atom is apparently going to be archived in December 15, 2022 (see Atom website for more info: https://github.blog/2022-06-08-sunsetting-atom/). You might want to change the example mentioned into other code editors or redirect to your "choosing an editor" website (https://textbook.nipraxis.org/choosing_editor.html).
Atom mentions on their near-future archiving notice (https://github.blog/2022-06-08-sunsetting-atom/) this option which seems like a VS code online version from Github (https://github.com/features/codespaces). It might be good to have information about it on this website. Let me know if you would like me to write a small section about it.
oesteban
reviewed
Jul 12, 2022
| @@ -107,7 +114,6 @@ The `%` operator on numbers gives you the remainder of integer division | |||
| 5.0 % 2.0 | |||
| ``` | |||
|
|
|||
| (true-and-false)= | |||
There was a problem hiding this comment.
Why is this removed? (please re-add)
There was a problem hiding this comment.
In binder they look like this. I was not sure if they were a mistake.
But now I see on the website version they look OK.
Should I re-add still? Should I look for a way the they do not look like that in Binder? I now assume they are there for a reason, do you know what is the function of those lines?
| @@ -186,7 +192,6 @@ different from MATLAB, which uses `~=`: | |||
| a != 1 | |||
| ``` | |||
|
|
|||
| (comparison-operators)= | |||
| @@ -269,7 +274,7 @@ print('not True:', not True) | |||
| print('not False:', not False) | |||
| ``` | |||
|
|
|||
| In fact, the logical operators will first force their arguments to be True or False before they give their answer. So, in the case of `and` or `or`, they force force their left and right arguents to be `bool` values, before they calculate the answer. So, in fact, you can use things other than exact True and False on either side of the `and` or `or`, as long as applying `bool(value)` to the thing to the left and right will produce a True or False value. See {doc}`truthiness` for more detail. | |||
| In fact, the logical operators will first force their arguments to be True or False before they give their answer. So, in the case of `and` or `or`, they force their left and right arguents to be `bool` values, before they calculate the answer. So, in fact, you can use things other than exact True and False on either side of the `and` or `or`, as long as applying `bool(value)` to the thing to the left and right will produce a True or False value. See {doc}`truthiness` for more detail. | |||
There was a problem hiding this comment.
Suggested change
| In fact, the logical operators will first force their arguments to be True or False before they give their answer. So, in the case of `and` or `or`, they force their left and right arguents to be `bool` values, before they calculate the answer. So, in fact, you can use things other than exact True and False on either side of the `and` or `or`, as long as applying `bool(value)` to the thing to the left and right will produce a True or False value. See {doc}`truthiness` for more detail. | |
| In fact, the logical operators will first force their arguments to be True or False before they give their answer. So, in the case of `and` or `or`, they force their left and right arguents to be `bool` values, before they calculate the answer. So, in fact, you can use things other than exact `True` and `False` on either side of the `and` or `or`, as long as applying `bool(value)` to the thing to the left and right will produce a True or False value. See {doc}`truthiness` for more detail. |
| @@ -689,7 +694,6 @@ you a reversed copy of the list: | |||
| my_list[::-1] | |||
| ``` | |||
|
|
|||
| (tuples)= | |||
issa-garcia
commented
Jul 12, 2022
oesteban
reviewed
Jul 12, 2022
| @@ -76,6 +76,7 @@ to PyCharm users). | |||
| * [Sublime text](https://www.sublimetext.com) | |||
| * [Emacs](https://emacs.org) | |||
| * [Spyder](https://www.spyder-ide.org) | |||
| * [GitHub Codespaces](https://github.com/features/codespaces) | |||
There was a problem hiding this comment.
Suggested change
| * [GitHub Codespaces](https://github.com/features/codespaces) |
Yes - I agree - I don't think this could replace the use of a text editor working on your own computer. |
added some minor additional missing information that I think would be useful for the reader stopped at line 176; will continue later
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-Added a small part to explain how to print results of not only the last line of code inside a cell (lines of .Rmd 75-81)
-Removed line 117 (a possible unintended text)
-Removed line 195 (a possible unintended text)
-Corrected a typo in line 277.
-Issue: On line 277 {doc}
truthinesshyperlink is not working in binder.--Removed line 697 (a possible unintended text)
--Issue: On line 747 {doc}
length_one_tupleshyperlink is not working in binder.-Modified line 876 to show results of 2nd line of code in the cell
//Stopped at end of section "Range", I will continue in 1 hour